From: Christian Brauner <brauner@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-nilfs@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/6] Filesystem page flags cleanup
Date: Fri, 4 Oct 2024 09:24:57 +0200 [thread overview]
Message-ID: <20241004-witzig-eisern-e47b5e26031a@brauner> (raw)
In-Reply-To: <20241002040111.1023018-1-willy@infradead.org>
On Wed, 02 Oct 2024 05:01:02 +0100, Matthew Wilcox (Oracle) wrote:
> I think this pile of patches makes most sense to take through the VFS
> tree. The first four continue the work begun in 02e1960aafac to make the
> mappedtodisk/owner_2 flag available to filesystems which don't use
> buffer heads. The last two remove uses of Private2 (we're achingly
> close to being rid of it entirely, but that doesn't seem like it'll
> land this merge window).
>
> [...]
Applied to the vfs.pagecache branch of the vfs/vfs.git tree.
Patches in the vfs.pagecache 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.pagecache
[1/6] fs: Move clearing of mappedtodisk to buffer.c
https://git.kernel.org/vfs/vfs/c/9c33d85e34c2
[2/6] nilfs2: Convert nilfs_copy_buffer() to use folios
https://git.kernel.org/vfs/vfs/c/a38117bc0de6
[3/6] mm: Remove PageMappedToDisk
https://git.kernel.org/vfs/vfs/c/a04d5f82fa38
[4/6] btrfs: Switch from using the private_2 flag to owner_2
https://git.kernel.org/vfs/vfs/c/a6752a6e7fb0
[5/6] ceph: Remove call to PagePrivate2()
https://git.kernel.org/vfs/vfs/c/fd15ba4cb00a
[6/6] migrate: Remove references to Private2
https://git.kernel.org/vfs/vfs/c/7735348d9f3a
prev parent reply other threads:[~2024-10-04 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 4:01 [PATCH 0/6] Filesystem page flags cleanup Matthew Wilcox (Oracle)
2024-10-02 4:01 ` [PATCH 1/6] fs: Move clearing of mappedtodisk to buffer.c Matthew Wilcox (Oracle)
2024-10-03 12:10 ` Jan Kara
2024-10-03 14:19 ` Matthew Wilcox
2024-10-02 4:01 ` [PATCH 2/6] nilfs2: Convert nilfs_copy_buffer() to use folios Matthew Wilcox (Oracle)
2024-10-02 13:11 ` Ryusuke Konishi
2024-10-02 4:01 ` [PATCH 3/6] mm: Remove PageMappedToDisk Matthew Wilcox (Oracle)
2024-10-03 12:11 ` Jan Kara
2024-10-02 4:01 ` [PATCH 4/6] btrfs: Switch from using the private_2 flag to owner_2 Matthew Wilcox (Oracle)
2024-10-03 17:09 ` Josef Bacik
2024-10-02 4:01 ` [PATCH 5/6] ceph: Remove call to PagePrivate2() Matthew Wilcox (Oracle)
2024-10-02 4:01 ` [PATCH 6/6] migrate: Remove references to Private2 Matthew Wilcox (Oracle)
2024-10-03 12:13 ` Jan Kara
2024-10-04 7:24 ` Christian Brauner [this message]
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=20241004-witzig-eisern-e47b5e26031a@brauner \
--to=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).