From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>
Cc: ke.wang@unisoc.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
Hao_hao.Wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix to add gc count stat in f2fs_gc_range
Date: Wed, 07 Jan 2026 03:30:26 +0000 [thread overview]
Message-ID: <176775662677.2218650.11507731650705298246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1766717764-19956-1-git-send-email-zhiguo.niu@unisoc.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 26 Dec 2025 10:56:04 +0800 you wrote:
> It missed the stat count in f2fs_gc_range.
>
> Cc: stable@kernel.org
> Fixes: 9bf1dcbdfdc8 ("f2fs: fix to account gc stats correctly")
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> ---
> V3: correct Fixes tags
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: fix to add gc count stat in f2fs_gc_range
https://git.kernel.org/jaegeuk/f2fs/c/761dac9073cd
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: Zhiguo Niu <zhiguo.niu@unisoc.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, Hao_hao.Wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix to add gc count stat in f2fs_gc_range
Date: Wed, 07 Jan 2026 03:30:26 +0000 [thread overview]
Message-ID: <176775662677.2218650.11507731650705298246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1766717764-19956-1-git-send-email-zhiguo.niu@unisoc.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 26 Dec 2025 10:56:04 +0800 you wrote:
> It missed the stat count in f2fs_gc_range.
>
> Cc: stable@kernel.org
> Fixes: 9bf1dcbdfdc8 ("f2fs: fix to account gc stats correctly")
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> ---
> V3: correct Fixes tags
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: fix to add gc count stat in f2fs_gc_range
https://git.kernel.org/jaegeuk/f2fs/c/761dac9073cd
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:[~2026-01-07 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 2:56 [f2fs-dev] [PATCH v3] f2fs: fix to add gc count stat in f2fs_gc_range Zhiguo Niu via Linux-f2fs-devel
2025-12-26 2:56 ` Zhiguo Niu
2025-12-26 3:01 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-12-26 3:01 ` Chao Yu
2026-01-07 3:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-01-07 3:30 ` [f2fs-dev] " 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=176775662677.2218650.11507731650705298246.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Hao_hao.Wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=zhiguo.niu@unisoc.com \
/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.