From: patchwork-bot+f2fs@kernel.org
To: yohan.joung <yohan.joung@sk.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, daehojeong@google.com,
pilhyun.kim@sk.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5 1/2] f2fs: add a method for calculating the remaining blocks in the current segment in LFS mode.
Date: Wed, 14 May 2025 15:40:35 +0000 [thread overview]
Message-ID: <174723723510.2412407.16198049270620230058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250512073611.718-1-yohan.joung@sk.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 May 2025 16:36:09 +0900 you wrote:
> In LFS mode, the previous segment cannot use invalid blocks,
> so the remaining blocks from the next_blkoff of the current segment
> to the end of the section are calculated.
>
> Signed-off-by: yohan.joung <yohan.joung@sk.com>
> ---
> fs/f2fs/segment.h | 23 +++++++++++++++++++----
> 1 file changed, 19 insertions(+), 4 deletions(-)
Here is the summary with links:
- [f2fs-dev,v5,1/2] f2fs: add a method for calculating the remaining blocks in the current segment in LFS mode.
https://git.kernel.org/jaegeuk/f2fs/c/91b11bd8152c
- [f2fs-dev,v5,2/2] f2fs: add ckpt_valid_blocks to the section entry
https://git.kernel.org/jaegeuk/f2fs/c/313d10d79a82
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-14 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 7:36 [PATCH v5 1/2] f2fs: add a method for calculating the remaining blocks in the current segment in LFS mode yohan.joung
2025-05-12 7:36 ` [PATCH v5 2/2] f2fs: add ckpt_valid_blocks to the section entry yohan.joung
2025-05-12 8:32 ` Chao Yu
2025-05-12 8:33 ` [PATCH v5 1/2] f2fs: add a method for calculating the remaining blocks in the current segment in LFS mode Chao Yu
2025-05-14 15:40 ` 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=174723723510.2412407.16198049270620230058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pilhyun.kim@sk.com \
--cc=yohan.joung@sk.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