From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new
Date: Thu, 14 Dec 2023 20:50:32 +0000 [thread overview]
Message-ID: <170258703206.30587.6882657417862323311.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231204180428.925779-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 4 Dec 2023 10:04:25 -0800 you wrote:
> If fsck can allocate a new zone, it'd be better to use that instead of
> allocating a new one.
>
> And, it modifies kernel messages.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/4] f2fs: allocate new section if it's not new
https://git.kernel.org/jaegeuk/f2fs/c/15a76c8014f9
- [f2fs-dev,2/4] f2fs: fix write pointers on zoned device after roll forward
https://git.kernel.org/jaegeuk/f2fs/c/9dad4d964291
- [f2fs-dev,3/4] f2fs: check write pointers when checkpoint=disable
https://git.kernel.org/jaegeuk/f2fs/c/aca90eea8a90
- [f2fs-dev,4/4] f2fs: let's finish or reset zones all the time
(no matching commit)
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:[~2023-12-14 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:04 [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new Jaegeuk Kim
2023-12-04 18:04 ` [f2fs-dev] [PATCH 2/4] f2fs: fix write pointers on zoned device after roll forward Jaegeuk Kim
2023-12-04 19:02 ` Daeho Jeong
2023-12-04 18:04 ` [f2fs-dev] [PATCH 3/4] f2fs: check write pointers when checkpoint=disable Jaegeuk Kim
2023-12-04 19:03 ` Daeho Jeong
2023-12-04 18:04 ` [f2fs-dev] [PATCH 4/4] f2fs: let's finish or reset zones all the time Jaegeuk Kim
2023-12-04 19:11 ` Daeho Jeong
2023-12-05 19:29 ` [f2fs-dev] [PATCH 4/4 v2] " Jaegeuk Kim
2023-12-04 18:53 ` [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new Daeho Jeong
2023-12-14 20:50 ` 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=170258703206.30587.6882657417862323311.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 \
/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).