From: patchwork-bot+f2fs@kernel.org
To: Sheng Yong <shengyong@oppo.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: alloc new section if curseg is not the first seg in its zone
Date: Wed, 12 Jun 2024 15:55:57 +0000 [thread overview]
Message-ID: <171820775704.32393.17458759004168978642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240530100158.762954-1-shengyong@oppo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 30 May 2024 18:01:58 +0800 you wrote:
> If curseg is not the first segment in its zone, the zone is not empty.
> A new section should be allocated and avoid resetting the old zone.
>
> Reviewed-by: Chao Yu <chao@kernel.org>
> Signed-off-by: Sheng Yong <shengyong@oppo.com>
> ---
> v2: remove and update inaccurate commit msg
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: alloc new section if curseg is not the first seg in its zone
https://git.kernel.org/jaegeuk/f2fs/c/76da333f4b93
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
next prev parent reply other threads:[~2024-06-12 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 11:24 [f2fs-dev] [PATCH] f2fs: avoid resetting non empty zone Sheng Yong via Linux-f2fs-devel
2024-05-29 11:27 ` Chao Yu
2024-05-30 10:01 ` [f2fs-dev] [PATCH v2] f2fs: alloc new section if curseg is not the first seg in its zone Sheng Yong via Linux-f2fs-devel
2024-06-12 15:55 ` patchwork-bot+f2fs [this message]
2024-06-12 15:55 ` [f2fs-dev] [PATCH] f2fs: avoid resetting non empty zone 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=171820775704.32393.17458759004168978642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong@oppo.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;
as well as URLs for NNTP newsgroup(s).