From: Christian Brauner <brauner@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, jun.li@nxp.com, djwong@kernel.org,
willy@infradead.org, akpm@linux-foundation.org
Subject: Re: [PATCH v5 1/2] filemap: add helper mapping_max_folio_size()
Date: Tue, 21 May 2024 16:22:09 +0200 [thread overview]
Message-ID: <20240521-beinbruch-kabine-0f83d1eab5e6@brauner> (raw)
In-Reply-To: <20240521114939.2541461-1-xu.yang_2@nxp.com>
On Tue, 21 May 2024 19:49:38 +0800, Xu Yang wrote:
> Add mapping_max_folio_size() to get the maximum folio size for this
> pagecache mapping.
>
>
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/2] filemap: add helper mapping_max_folio_size()
https://git.kernel.org/vfs/vfs/c/0c31d63eebdd
[2/2] iomap: fault in smaller chunks for non-large folio mappings
https://git.kernel.org/vfs/vfs/c/63ba6f07d115
next prev parent reply other threads:[~2024-05-21 14:22 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 ` Christian Brauner [this message]
2024-05-24 6:21 ` [PATCH v5 1/2] filemap: add helper mapping_max_folio_size() Ritesh Harjani
2024-05-24 8:03 ` Christoph Hellwig
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=20240521-beinbruch-kabine-0f83d1eab5e6@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.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