From: Chao Yu <chao@kernel.org>
To: Baolin Liu <liubaolin12138@163.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v1] f2fs: simplify list initialization in f2fs_recover_fsync_data()
Date: Wed, 12 Nov 2025 19:05:14 +0800 [thread overview]
Message-ID: <bea78bf3-ee75-431e-b65b-1525d26f6589@kernel.org> (raw)
In-Reply-To: <20251111121728.29433-1-liubaolin12138@163.com>
On 11/11/25 20:17, Baolin Liu wrote:
> From: Baolin Liu <liubaolin@kylinos.cn>
>
> In f2fs_recover_fsync_data(),use LIST_HEAD() to declare and
> initialize the list_head in one step instead of using
> INIT_LIST_HEAD() separately.
>
> No functional change.
>
> Signed-off-by: Baolin Liu <liubaolin@kylinos.cn>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-11-12 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 12:17 [PATCH v1] f2fs: simplify list initialization in f2fs_recover_fsync_data() Baolin Liu
2025-11-12 11:05 ` Chao Yu [this message]
2025-11-24 18:50 ` [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=bea78bf3-ee75-431e-b65b-1525d26f6589@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=liubaolin@kylinos.cn \
/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