From: Christoph Hellwig <hch@infradead.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: brauner@kernel.org, djwong@kernel.org, willy@infradead.org,
akpm@linux-foundation.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
jun.li@nxp.com
Subject: Re: [PATCH v5 1/2] filemap: add helper mapping_max_folio_size()
Date: Fri, 24 May 2024 01:03:37 -0700 [thread overview]
Message-ID: <ZlBJ2YviFb7m_Iej@infradead.org> (raw)
In-Reply-To: <20240521114939.2541461-1-xu.yang_2@nxp.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-05-24 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 11:49 Xu Yang
2024-05-21 11:49 ` [PATCH v5 2/2] iomap: fault in smaller chunks for non-large folio mappings Xu Yang
2024-05-24 8:03 ` Christoph Hellwig
2024-05-24 12:18 ` Matthew Wilcox
2024-05-21 14:22 ` [PATCH v5 1/2] filemap: add helper mapping_max_folio_size() Christian Brauner
2024-05-24 6:21 ` Ritesh Harjani
2024-05-24 8:03 ` Christoph Hellwig [this message]
2024-05-24 12:17 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZlBJ2YviFb7m_Iej@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jun.li@nxp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xu.yang_2@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox