From: patchwork-bot+f2fs@kernel.org
To: Kohei Enju <enjuk@amazon.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, axboe@kernel.dk,
damien.lemoal@wdc.com, chaitanya.kulkarni@wdc.com,
johannes.thumshirn@wdc.com, jaegeuk@kernel.org,
kohei.enju@gmail.com
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: remove unnecessary null checking
Date: Thu, 06 Feb 2025 18:40:42 +0000 [thread overview]
Message-ID: <173886724251.1614734.17651671887403590690.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250202043253.64389-1-enjuk@amazon.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 2 Feb 2025 13:32:53 +0900 you wrote:
> When __GFP_DIRECT_RECLAIM (included in both GFP_NOIO and GFP_KERNEL) is
> specified, bio_alloc_bioset() never fails to allocate a bio.
> Commit 67883ade7a98 ("f2fs: remove FAULT_ALLOC_BIO") replaced
> f2fs_bio_alloc() with bio_alloc_bioset(), but null checking after
> bio_alloc_bioset() was still left.
>
> Fixes: 67883ade7a98 ("f2fs: remove FAULT_ALLOC_BIO")
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v1] f2fs: remove unnecessary null checking
https://git.kernel.org/jaegeuk/f2fs/c/53333cdf5b03
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-02-06 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 4:32 [PATCH v1] f2fs: remove unnecessary null checking Kohei Enju
2025-02-02 14:20 ` [PATCH] " Markus Elfring
2025-02-02 15:05 ` [PATCH v1] " Jens Axboe
2025-02-06 1:59 ` Chao Yu
2025-02-06 18:40 ` 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=173886724251.1614734.17651671887403590690.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=enjuk@amazon.com \
--cc=jaegeuk@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=kohei.enju@gmail.com \
--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