From: patchwork-bot+f2fs@kernel.org
To: mason.zhang <masonzhang.linuxer@gmail.com>
Cc: chao@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: merge the two conditions to avoid code duplication
Date: Thu, 24 Jul 2025 20:30:10 +0000 [thread overview]
Message-ID: <175338901026.2519964.16198621184448578981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723145837.187089-1-masonzhang.linuxer@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 23 Jul 2025 22:58:37 +0800 you wrote:
> No functional changes.
>
> Signed-off-by: mason.zhang <masonzhang.linuxer@gmail.com>
> ---
> fs/f2fs/gc.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
Here is the summary with links:
- [f2fs-dev] f2fs: merge the two conditions to avoid code duplication
https://git.kernel.org/jaegeuk/f2fs/c/b93bf64e349b
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-07-24 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 14:58 mason.zhang
2025-07-24 2:51 ` Chao Yu
2025-07-24 20:30 ` 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=175338901026.2519964.16198621184448578981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masonzhang.linuxer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®