From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: clean up w/ bio_add_folio_nofail()
Date: Tue, 11 Nov 2025 22:50:10 +0000 [thread overview]
Message-ID: <176290141074.3596344.11323424525560613552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251014062704.1734984-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 14 Oct 2025 14:27:01 +0800 you wrote:
> In add_bio_entry(), adding a page to newly allocated bio should never fail,
> let's use bio_add_folio_nofail() instead of bio_add_page() & unnecessary
> error handling for cleanup.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/data.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/4] f2fs: clean up w/ bio_add_folio_nofail()
https://git.kernel.org/jaegeuk/f2fs/c/6862f6948aa3
- [f2fs-dev,2/4] f2fs: convert add_ipu_page() to use folio
https://git.kernel.org/jaegeuk/f2fs/c/22de407ee7fd
- [f2fs-dev,3/4] f2fs: use f2fs_filemap_get_folio() instead of f2fs_pagecache_get_page()
https://git.kernel.org/jaegeuk/f2fs/c/10005e36127b
- [f2fs-dev,4/4] f2fs: use f2fs_filemap_get_folio() to support fault injection
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-11 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 6:27 [PATCH 1/4] f2fs: clean up w/ bio_add_folio_nofail() Chao Yu
2025-10-14 6:27 ` [PATCH 2/4] f2fs: convert add_ipu_page() to use folio Chao Yu
2025-10-14 6:27 ` [PATCH 3/4] f2fs: use f2fs_filemap_get_folio() instead of f2fs_pagecache_get_page() Chao Yu
2025-10-14 6:27 ` [PATCH 4/4] f2fs: use f2fs_filemap_get_folio() to support fault injection Chao Yu
2025-11-11 22:50 ` patchwork-bot+f2fs [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=176290141074.3596344.11323424525560613552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox