From: Matthew Wilcox <willy@infradead.org>
To: linux-fsdevel@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>,
Mike Marshall <hubcap@omnibond.com>,
Martin Brandenburg <martin@omnibond.com>,
devel@lists.orangefs.org, David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org, Miklos Szeredi <miklos@szeredi.hu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Tyler Hicks <code@tyhicks.com>,
ecryptfs@vger.kernel.org,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
linux-nilfs@vger.kernel.org, reiserfs-devel@vger.kernel.org
Subject: [6.12] Conversion of aops->write_end to use a folio
Date: Wed, 10 Jul 2024 22:40:19 +0100 [thread overview]
Message-ID: <Zo7_w-BjbbbrxadX@casper.infradead.org> (raw)
For the 6.12 merge window, I intend to submit a patch series loosely
similar to the one you can find at
http://git.infradead.org/?p=users/willy/pagecache.git;a=shortlog;h=refs/heads/write-end
(aka git://git.infradead.org/users/willy/pagecache.git write-end)
This is split into a few pieces:
- Directory handling conversion for ufs, sysv, minix & qnx6, all posted
recently.
- Various prep patches in reiserfs, jffs2, block fops, nilfs2, ntfs3,
ecryptfs, f2fs, fuse, orangefs and vboxsf
- The big bang conversion that is now appropriately trivial in each
affected filesystem.
It would be nice to get sign-offs from the various fs maintainers on
the prep patches. I'll send those out in the next 24 hours. If you
want to take them through your tree, I ask that you do that for 6.11 so
we're not juggling git trees trying to resolve conflicts in 6.12.
I don't think we need signoffs from the various fs maintainers for the
big bang patch as the individual changes are so trivial. But if you
want to give it a look-over, the more eyes the better.
reply other threads:[~2024-07-10 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zo7_w-BjbbbrxadX@casper.infradead.org \
--to=willy@infradead.org \
--cc=chao@kernel.org \
--cc=code@tyhicks.com \
--cc=devel@lists.orangefs.org \
--cc=dwmw2@infradead.org \
--cc=ecryptfs@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=hubcap@omnibond.com \
--cc=jaegeuk@kernel.org \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=martin@omnibond.com \
--cc=miklos@szeredi.hu \
--cc=reiserfs-devel@vger.kernel.org \
--cc=richard@nod.at \
/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).