From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
daehojeong@google.com, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: zone: fix to calculate first_zoned_segno correctly
Date: Thu, 10 Apr 2025 04:10:41 +0000 [thread overview]
Message-ID: <174425824176.3146257.18250969661492747760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250325080646.3291947-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 25 Mar 2025 16:06:45 +0800 you wrote:
> A zoned device can has both conventional zones and sequential zones,
> so we should not treat first segment of zoned device as first_zoned_segno,
> instead, we need to check zone type for each zone during traversing zoned
> device to find first_zoned_segno.
>
> Otherwise, for below case, first_zoned_segno will be 0, which could be
> wrong.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: zone: fix to calculate first_zoned_segno correctly
(no matching commit)
- [f2fs-dev,v2,2/2] f2fs: zone: fix to avoid inconsistence in between SIT and SSA
https://git.kernel.org/jaegeuk/f2fs/c/773704c1ef96
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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: zone: fix to calculate first_zoned_segno correctly
Date: Thu, 10 Apr 2025 04:10:41 +0000 [thread overview]
Message-ID: <174425824176.3146257.18250969661492747760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250325080646.3291947-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 25 Mar 2025 16:06:45 +0800 you wrote:
> A zoned device can has both conventional zones and sequential zones,
> so we should not treat first segment of zoned device as first_zoned_segno,
> instead, we need to check zone type for each zone during traversing zoned
> device to find first_zoned_segno.
>
> Otherwise, for below case, first_zoned_segno will be 0, which could be
> wrong.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: zone: fix to calculate first_zoned_segno correctly
(no matching commit)
- [f2fs-dev,v2,2/2] f2fs: zone: fix to avoid inconsistence in between SIT and SSA
https://git.kernel.org/jaegeuk/f2fs/c/773704c1ef96
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-04-10 4:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 8:06 [f2fs-dev] [PATCH v2 1/2] f2fs: zone: fix to calculate first_zoned_segno correctly Chao Yu via Linux-f2fs-devel
2025-03-25 8:06 ` Chao Yu
2025-03-25 8:06 ` [f2fs-dev] [PATCH v2 2/2] f2fs: zone: fix to avoid inconsistence in between SIT and SSA Chao Yu via Linux-f2fs-devel
2025-03-25 8:06 ` Chao Yu
2025-03-25 22:33 ` [f2fs-dev] [PATCH v2 1/2] f2fs: zone: fix to calculate first_zoned_segno correctly Daeho Jeong
2025-03-25 22:33 ` Daeho Jeong
2025-03-28 3:29 ` Jaegeuk Kim via Linux-f2fs-devel
2025-03-28 3:29 ` Jaegeuk Kim
2025-03-28 4:02 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-28 4:02 ` Chao Yu
2025-03-31 5:41 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-31 5:41 ` Chao Yu
2025-04-10 4:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-04-10 4:10 ` [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=174425824176.3146257.18250969661492747760.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.