From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yangyang Zang <zangyangyang66@gmail.com>
Cc: zangyangyang1@xiaomi.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: clean up the type parameter in f2fs_sync_meta_pages()
Date: Mon, 19 Jan 2026 13:50:44 +0000 [thread overview]
Message-ID: <176883064431.1419958.7644951813571234460.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112074635.3405176-1-zangyangyang1@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 Jan 2026 15:46:35 +0800 you wrote:
> Clean up code to improve readability, no logic changes.
>
> Signed-off-by: Yangyang Zang <zangyangyang1@xiaomi.com>
> ---
> fs/f2fs/checkpoint.c | 15 +++++++--------
> fs/f2fs/f2fs.h | 4 ++--
> fs/f2fs/file.c | 2 +-
> 3 files changed, 10 insertions(+), 11 deletions(-)
Here is the summary with links:
- [f2fs-dev] f2fs: clean up the type parameter in f2fs_sync_meta_pages()
https://git.kernel.org/jaegeuk/f2fs/c/f7b929eda1f1
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
prev parent reply other threads:[~2026-01-19 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:46 [f2fs-dev] [PATCH] f2fs: clean up the type parameter in f2fs_sync_meta_pages() Yangyang Zang
2026-01-12 9:27 ` Chao Yu via Linux-f2fs-devel
2026-01-19 13:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=176883064431.1419958.7644951813571234460.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=zangyangyang1@xiaomi.com \
--cc=zangyangyang66@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