From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Christoph Hellwig <hch@lst.de>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: return bool from __f2fs_write_meta_folio
Date: Thu, 08 May 2025 16:30:34 +0000 [thread overview]
Message-ID: <174672183439.2971823.3514035495469424112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250505092613.3451524-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 5 May 2025 11:25:58 +0200 you wrote:
> __f2fs_write_meta_folio can only return 0 or AOP_WRITEPAGE_ACTIVATE.
> As part of phasing out AOP_WRITEPAGE_ACTIVATE, switch to a bool return
> instead.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/f2fs/checkpoint.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/4] f2fs: return bool from __f2fs_write_meta_folio
https://git.kernel.org/jaegeuk/f2fs/c/39122e454419
- [f2fs-dev,2/4] f2fs: don't return AOP_WRITEPAGE_ACTIVATE from f2fs_write_single_data_page
(no matching commit)
- [f2fs-dev,3/4] f2fs: simplify return value handling in f2fs_fsync_node_pages
(no matching commit)
- [f2fs-dev,4/4] f2f2: return bool from __write_node_folio
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: return bool from __f2fs_write_meta_folio
Date: Thu, 08 May 2025 16:30:34 +0000 [thread overview]
Message-ID: <174672183439.2971823.3514035495469424112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250505092613.3451524-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 5 May 2025 11:25:58 +0200 you wrote:
> __f2fs_write_meta_folio can only return 0 or AOP_WRITEPAGE_ACTIVATE.
> As part of phasing out AOP_WRITEPAGE_ACTIVATE, switch to a bool return
> instead.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/f2fs/checkpoint.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/4] f2fs: return bool from __f2fs_write_meta_folio
https://git.kernel.org/jaegeuk/f2fs/c/39122e454419
- [f2fs-dev,2/4] f2fs: don't return AOP_WRITEPAGE_ACTIVATE from f2fs_write_single_data_page
(no matching commit)
- [f2fs-dev,3/4] f2fs: simplify return value handling in f2fs_fsync_node_pages
(no matching commit)
- [f2fs-dev,4/4] f2f2: return bool from __write_node_folio
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-05-08 16:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 9:25 [f2fs-dev] cleanup AOP_WRITEPAGE_ACTIVATE use in f2fs Christoph Hellwig
2025-05-05 9:25 ` Christoph Hellwig
2025-05-05 9:25 ` [f2fs-dev] [PATCH 1/4] f2fs: return bool from __f2fs_write_meta_folio Christoph Hellwig
2025-05-05 9:25 ` Christoph Hellwig
2025-05-07 6:22 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 6:22 ` Chao Yu
2025-05-08 16:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-05-08 16:30 ` [f2fs-dev] " patchwork-bot+f2fs
2025-05-05 9:25 ` [f2fs-dev] [PATCH 2/4] f2fs: don't return AOP_WRITEPAGE_ACTIVATE from f2fs_write_single_data_page Christoph Hellwig
2025-05-05 9:25 ` Christoph Hellwig
2025-05-07 6:28 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 6:28 ` Chao Yu
2025-05-07 6:44 ` [f2fs-dev] " Christoph Hellwig
2025-05-07 6:44 ` Christoph Hellwig
2025-05-07 7:09 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 7:09 ` Chao Yu
2025-05-05 9:26 ` [f2fs-dev] [PATCH 3/4] f2fs: simplify return value handling in f2fs_fsync_node_pages Christoph Hellwig
2025-05-05 9:26 ` Christoph Hellwig
2025-05-07 7:19 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 7:19 ` Chao Yu
2025-05-05 9:26 ` [f2fs-dev] [PATCH 4/4] f2f2: return bool from __write_node_folio Christoph Hellwig
2025-05-05 9:26 ` Christoph Hellwig
2025-05-07 7:29 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 7:29 ` Chao Yu
2025-05-07 7:38 ` [f2fs-dev] cleanup AOP_WRITEPAGE_ACTIVATE use in f2fs Chao Yu via Linux-f2fs-devel
2025-05-07 7:38 ` Chao Yu
2025-05-07 7:48 ` [f2fs-dev] " Christoph Hellwig
2025-05-07 7:48 ` Christoph Hellwig
2025-05-07 8:13 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-07 8:13 ` Chao Yu
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=174672183439.2971823.3514035495469424112.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.