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 v2 1/3] f2fs: use memalloc_retry_wait() as much as possible
Date: Mon, 24 Nov 2025 18:50:11 +0000 [thread overview]
Message-ID: <176401021111.42009.2835774626378827103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251112014749.2006439-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 12 Nov 2025 09:47:47 +0800 you wrote:
> memalloc_retry_wait() is recommended in memory allocation retry logic,
> use it as much as possible.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> use memalloc_retry_wait() instead of f2fs_io_schedule_timeout()
> fs/f2fs/segment.c | 2 +-
> fs/f2fs/super.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Here is the summary with links:
- [f2fs-dev,v2,1/3] f2fs: use memalloc_retry_wait() as much as possible
https://git.kernel.org/jaegeuk/f2fs/c/00e24c488596
- [f2fs-dev,v2,2/3] f2fs: introduce f2fs_schedule_timeout()
https://git.kernel.org/jaegeuk/f2fs/c/517eb4747ad8
- [f2fs-dev,v2,3/3] f2fs: change default schedule timeout value
https://git.kernel.org/jaegeuk/f2fs/c/2f4c126cc08b
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-24 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 1:47 [PATCH v2 1/3] f2fs: use memalloc_retry_wait() as much as possible Chao Yu
2025-11-12 1:47 ` [PATCH v2 2/3] f2fs: introduce f2fs_schedule_timeout() Chao Yu
2025-11-12 1:47 ` [PATCH v2 3/3] f2fs: change default schedule timeout value Chao Yu
2025-11-24 18: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=176401021111.42009.2835774626378827103.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