From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: ebiggers@kernel.org, brauner@kernel.org, tytso@mit.edu,
djwong@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, adilger.kernel@dilger.ca,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 01/11] fscrypt: pass a real sector_t to fscrypt_zeroout_range_inline_crypt
Date: Tue, 17 Feb 2026 21:14:31 +0000 [thread overview]
Message-ID: <177136287109.643511.9798324970398190582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251118062159.2358085-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe <axboe@kernel.dk>:
On Tue, 18 Nov 2025 07:21:44 +0100 you wrote:
> While the pblk argument to fscrypt_zeroout_range_inline_crypt is
> declared as a sector_t it actually is interpreted as a logical block
> size unit, which is highly unusual. Switch to passing the 512 byte
> units that sector_t is defined for.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Eric Biggers <ebiggers@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,01/11] fscrypt: pass a real sector_t to fscrypt_zeroout_range_inline_crypt
https://git.kernel.org/jaegeuk/f2fs/c/c22756a9978e
- [f2fs-dev,02/11] fscrypt: keep multiple bios in flight in fscrypt_zeroout_range_inline_crypt
https://git.kernel.org/jaegeuk/f2fs/c/bc26e2efa2c5
- [f2fs-dev,03/11] fscrypt: pass a byte offset to fscrypt_generate_dun
(no matching commit)
- [f2fs-dev,04/11] fscrypt: pass a byte offset to fscrypt_mergeable_bio
(no matching commit)
- [f2fs-dev,05/11] fscrypt: pass a byte offset to fscrypt_set_bio_crypt_ctx
(no matching commit)
- [f2fs-dev,06/11] fscrypt: pass a byte offset to fscrypt_zeroout_range_inline_crypt
(no matching commit)
- [f2fs-dev,07/11] fscrypt: pass a byte length to fscrypt_zeroout_range_inline_crypt
(no matching commit)
- [f2fs-dev,08/11] fscrypt: return a byte offset from bh_get_inode_and_lblk_num
(no matching commit)
- [f2fs-dev,09/11] fscrypt: pass a byte offset to fscrypt_zeroout_range
(no matching commit)
- [f2fs-dev,10/11] fscrypt: pass a byte length to fscrypt_zeroout_range
(no matching commit)
- [f2fs-dev,11/11] fscrypt: pass a real sector_t to fscrypt_zeroout_range
(no matching commit)
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:[~2026-02-17 21:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 6:21 fscrypt API cleanups Christoph Hellwig
2025-11-18 6:21 ` [PATCH 01/11] fscrypt: pass a real sector_t to fscrypt_zeroout_range_inline_crypt Christoph Hellwig
2026-02-17 21:14 ` patchwork-bot+f2fs [this message]
2025-11-18 6:21 ` [PATCH 02/11] fscrypt: keep multiple bios in flight in fscrypt_zeroout_range_inline_crypt Christoph Hellwig
2025-11-18 6:21 ` [PATCH 03/11] fscrypt: pass a byte offset to fscrypt_generate_dun Christoph Hellwig
2025-11-18 6:21 ` [PATCH 04/11] fscrypt: pass a byte offset to fscrypt_mergeable_bio Christoph Hellwig
2025-11-22 18:17 ` Eric Biggers
2025-11-24 14:16 ` Christoph Hellwig
2025-11-18 6:21 ` [PATCH 05/11] fscrypt: pass a byte offset to fscrypt_set_bio_crypt_ctx Christoph Hellwig
2025-11-18 6:21 ` [PATCH 06/11] fscrypt: pass a byte offset to fscrypt_zeroout_range_inline_crypt Christoph Hellwig
2025-11-18 6:21 ` [PATCH 07/11] fscrypt: pass a byte length " Christoph Hellwig
2025-11-18 6:21 ` [PATCH 08/11] fscrypt: return a byte offset from bh_get_inode_and_lblk_num Christoph Hellwig
2025-11-22 18:19 ` Eric Biggers
2025-11-18 6:21 ` [PATCH 09/11] fscrypt: pass a byte offset to fscrypt_zeroout_range Christoph Hellwig
2025-11-18 6:21 ` [PATCH 10/11] fscrypt: pass a byte length " Christoph Hellwig
2025-11-22 18:29 ` Eric Biggers
2025-11-24 14:17 ` Christoph Hellwig
2025-11-18 6:21 ` [PATCH 11/11] fscrypt: pass a real sector_t " Christoph Hellwig
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=177136287109.643511.9798324970398190582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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