From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: patchwork-bot+f2fs@kernel.org, chao@kernel.org,
linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/4] f2fs: Remove uses of writepage
Date: Wed, 12 Mar 2025 01:22:41 +0000 [thread overview]
Message-ID: <Z9Dh4UL7uTm3cQM3@google.com> (raw)
In-Reply-To: <Z9DSym8c9h53Xmr8@casper.infradead.org>
On 03/12, Matthew Wilcox wrote:
> On Tue, Mar 11, 2025 at 07:50:38PM +0000, patchwork-bot+f2fs@kernel.org wrote:
> > Hello:
> >
> > This series was applied to jaegeuk/f2fs.git (dev)
> > by Jaegeuk Kim <jaegeuk@kernel.org>:
>
> Thanks!
>
> FWIW, I have a tree with 75 patches in it on top of this that do more
> folio conversion work. It's not done yet; maybe another 200 patches to
> go? I don't think it's worth posting at this point in the cycle, so
> I'll wait until -rc1 to post, by which point it'll probably be much
> larger.
Ok, thanks for the work! Will keep an eye on.
next prev parent reply other threads:[~2025-03-12 1:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 18:21 [PATCH 0/4] f2fs: Remove uses of writepage Matthew Wilcox (Oracle)
2025-03-07 18:21 ` [PATCH 1/4] f2fs: Remove check for ->writepage Matthew Wilcox (Oracle)
2025-03-11 11:48 ` Chao Yu
2025-03-07 18:21 ` [PATCH 2/4] f2fs: Remove f2fs_write_data_page() Matthew Wilcox (Oracle)
2025-03-11 11:48 ` Chao Yu
2025-03-07 18:21 ` [PATCH 3/4] f2fs: Remove f2fs_write_meta_page() Matthew Wilcox (Oracle)
2025-03-11 11:49 ` Chao Yu
2025-03-07 18:21 ` [PATCH 4/4] f2fs: Remove f2fs_write_node_page() Matthew Wilcox (Oracle)
2025-03-11 11:49 ` Chao Yu
2025-03-07 20:39 ` [PATCH 0/4] f2fs: Remove uses of writepage Jaegeuk Kim
2025-03-07 20:48 ` Matthew Wilcox
2025-03-07 22:13 ` Jaegeuk Kim
2025-03-11 19:50 ` [f2fs-dev] " patchwork-bot+f2fs
2025-03-12 0:18 ` Matthew Wilcox
2025-03-12 1:22 ` Jaegeuk Kim [this message]
2025-03-14 15:57 ` Matthew Wilcox
2025-03-14 21:38 ` Jaegeuk Kim
2025-03-26 3:37 ` Matthew Wilcox
2025-03-27 22:27 ` Jaegeuk Kim
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=Z9Dh4UL7uTm3cQM3@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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).