All of lore.kernel.org
 help / color / mirror / Atom feed
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: ignore valid ratio when free section count is low
Date: Thu, 24 Jul 2025 20:30:12 +0000	[thread overview]
Message-ID: <175338901299.2519964.7208919270936337472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250718220431.2290301-1-daeho43@gmail.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Fri, 18 Jul 2025 15:04:31 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> Otherwise F2FS will not do GC in background in low free section.
> 
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
>  fs/f2fs/gc.c | 18 ++++++++++++------
>  1 file changed, 12 insertions(+), 6 deletions(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: ignore valid ratio when free section count is low
    https://git.kernel.org/jaegeuk/f2fs/c/e6d5e789c3b2

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: ignore valid ratio when free section count is low
Date: Thu, 24 Jul 2025 20:30:12 +0000	[thread overview]
Message-ID: <175338901299.2519964.7208919270936337472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250718220431.2290301-1-daeho43@gmail.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Fri, 18 Jul 2025 15:04:31 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> Otherwise F2FS will not do GC in background in low free section.
> 
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
>  fs/f2fs/gc.c | 18 ++++++++++++------
>  1 file changed, 12 insertions(+), 6 deletions(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: ignore valid ratio when free section count is low
    https://git.kernel.org/jaegeuk/f2fs/c/e6d5e789c3b2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-07-24 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 22:04 [f2fs-dev] [PATCH] f2fs: ignore valid ratio when free section count is low Daeho Jeong
2025-07-18 22:04 ` Daeho Jeong
2025-07-22  3:44 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-07-22  3:44   ` Chao Yu
2025-07-24 20:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-07-24 20:30   ` 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=175338901299.2519964.7208919270936337472.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.