From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Baolin Liu <liubaolin12138@163.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, liubaolin@kylinos.cn
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: simplify list initialization in f2fs_recover_fsync_data()
Date: Mon, 24 Nov 2025 18:50:09 +0000 [thread overview]
Message-ID: <176401020949.42009.2139954343027110885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251111121728.29433-1-liubaolin12138@163.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Nov 2025 20:17:28 +0800 you 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v1] f2fs: simplify list initialization in f2fs_recover_fsync_data()
https://git.kernel.org/jaegeuk/f2fs/c/82fbca2067aa
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: Baolin Liu <liubaolin12138@163.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, liubaolin@kylinos.cn,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: simplify list initialization in f2fs_recover_fsync_data()
Date: Mon, 24 Nov 2025 18:50:09 +0000 [thread overview]
Message-ID: <176401020949.42009.2139954343027110885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251111121728.29433-1-liubaolin12138@163.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Nov 2025 20:17:28 +0800 you 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v1] f2fs: simplify list initialization in f2fs_recover_fsync_data()
https://git.kernel.org/jaegeuk/f2fs/c/82fbca2067aa
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:[~2025-11-24 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 12:17 [f2fs-dev] [PATCH v1] f2fs: simplify list initialization in f2fs_recover_fsync_data() Baolin Liu
2025-11-11 12:17 ` Baolin Liu
2025-11-12 11:05 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-11-12 11:05 ` Chao Yu
2025-11-24 18:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=176401020949.42009.2139954343027110885.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=liubaolin@kylinos.cn \
--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.