From: patchwork-bot+f2fs@kernel.org
To: Kelvin Zhang <zhangxp1998@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v9 00/11] f2fs: prepare metadata layouts for runtime block sizes
Date: Tue, 08 Sep 2026 20:00:06 +0000 [thread overview]
Message-ID: <178889760650.3720652.823497895203817513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1788479509.git.zhangxp1998@gmail.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 3 Sep 2026 16:54:16 -0700 you wrote:
> F2FS currently describes several on-disk metadata layouts and filesystem
> geometry values with constants derived from PAGE_SIZE or a fixed 4KB block
> size. This series derives those values from the mounted filesystem's block
> size instead, as preparation for supporting filesystem blocks smaller than
> PAGE_SIZE.
>
> The patches initialize sb_info early, describe the SIT, NAT, orphan, dentry,
> node, and xattr layouts dynamically, parameterize sector/byte/block
> conversion helpers, and derive node-tree geometry at runtime.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v9,01/11] f2fs: initialize sb_info early in f2fs_fill_super
https://git.kernel.org/jaegeuk/f2fs/c/425a464e82a1
- [f2fs-dev,v9,02/11] f2fs: describe SIT block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/b41496b999b3
- [f2fs-dev,v9,03/11] f2fs: describe NAT block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/4b1fbe38ce5b
- [f2fs-dev,v9,04/11] f2fs: describe orphan block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/0e346faac20c
- [f2fs-dev,v9,05/11] f2fs: describe dentry block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/2f5562816fac
- [f2fs-dev,v9,06/11] f2fs: describe {i, d, id}node block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/49d39bc4b877
- [f2fs-dev,v9,07/11] f2fs: describe xattr block layout dynamically
https://git.kernel.org/jaegeuk/f2fs/c/fbf612f85437
- [f2fs-dev,v9,08/11] f2fs: parameterize sector conversion macros
https://git.kernel.org/jaegeuk/f2fs/c/87f159c1492f
- [f2fs-dev,v9,09/11] f2fs: parameterize byte and block conversion macros
https://git.kernel.org/jaegeuk/f2fs/c/7c8fd5156c90
- [f2fs-dev,v9,10/11] f2fs: describe node tree geometry dynamically
https://git.kernel.org/jaegeuk/f2fs/c/a4bfdfc5d3d8
- [f2fs-dev,v9,11/11] f2fs: parameterize block size and mask macros
https://git.kernel.org/jaegeuk/f2fs/c/6a0dda6838b6
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:[~2026-09-08 20:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:54 Kelvin Zhang
2026-09-03 23:54 ` [PATCH v9 01/11] f2fs: initialize sb_info early in f2fs_fill_super Kelvin Zhang
2026-09-04 1:48 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 02/11] f2fs: describe SIT block layout dynamically Kelvin Zhang
2026-09-04 1:54 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 03/11] f2fs: describe NAT " Kelvin Zhang
2026-09-04 1:55 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 04/11] f2fs: describe orphan " Kelvin Zhang
2026-09-04 1:56 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 05/11] f2fs: describe dentry " Kelvin Zhang
2026-09-04 1:58 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 06/11] f2fs: describe {i,d,id}node " Kelvin Zhang
2026-09-04 2:08 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 07/11] f2fs: describe xattr " Kelvin Zhang
2026-09-04 2:15 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 08/11] f2fs: parameterize sector conversion macros Kelvin Zhang
2026-09-04 2:16 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 09/11] f2fs: parameterize byte and block " Kelvin Zhang
2026-09-04 2:17 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 10/11] f2fs: describe node tree geometry dynamically Kelvin Zhang
2026-09-04 2:18 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 11/11] f2fs: parameterize block size and mask macros Kelvin Zhang
2026-09-04 2:20 ` Chao Yu
2026-09-08 20:00 ` 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=178889760650.3720652.823497895203817513.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=zhangxp1998@gmail.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
all inboxes | Powered by JetHome®