From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Daeho Jeong <daeho43@gmail.com>
Cc: daehojeong@google.com, kernel-team@android.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: make sure zoned device GC to use FG_GC in shortage of free section
Date: Tue, 24 Jun 2025 00:40:52 +0000 [thread overview]
Message-ID: <175072565225.3346761.9321054958830239968.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250529222532.1088106-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 29 May 2025 15:25:32 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> We already use FG_GC when we have free sections under
> gc_boost_zoned_gc_percent. So, let's make it consistent.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: make sure zoned device GC to use FG_GC in shortage of free section
https://git.kernel.org/jaegeuk/f2fs/c/24bf3ee37fb8
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: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
daehojeong@google.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: make sure zoned device GC to use FG_GC in shortage of free section
Date: Tue, 24 Jun 2025 00:40:52 +0000 [thread overview]
Message-ID: <175072565225.3346761.9321054958830239968.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250529222532.1088106-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 29 May 2025 15:25:32 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> We already use FG_GC when we have free sections under
> gc_boost_zoned_gc_percent. So, let's make it consistent.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: make sure zoned device GC to use FG_GC in shortage of free section
https://git.kernel.org/jaegeuk/f2fs/c/24bf3ee37fb8
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-06-24 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 22:25 [f2fs-dev] [PATCH] f2fs: make sure zoned device GC to use FG_GC in shortage of free section Daeho Jeong
2025-05-29 22:25 ` Daeho Jeong
2025-06-03 6:58 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-06-03 6:58 ` Chao Yu
2025-06-24 0:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-06-24 0:40 ` patchwork-bot+f2fs
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=175072565225.3346761.9321054958830239968.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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.