From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Baokun Li <libaokun@linux.alibaba.com>, Jan Kara <jack@suse.cz>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Ritesh Harjani <ritesh.list@gmail.com>,
Zhang Yi <yi.zhang@huawei.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
Chao Yu <chao@kernel.org>
Subject: Re: [PATCH v3 03/17] blk-crypto: Allow control over whether hardware is used
Date: Mon, 13 Jul 2026 10:32:56 +0200 [thread overview]
Message-ID: <20260713083256.GA4304@lst.de> (raw)
In-Reply-To: <20260713023708.9245-4-ebiggers@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
Theodore Ts'o <tytso@mit.edu>, Zhang Yi <yi.zhang@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-fscrypt@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Baokun Li <libaokun@linux.alibaba.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [f2fs-dev] [PATCH v3 03/17] blk-crypto: Allow control over whether hardware is used
Date: Mon, 13 Jul 2026 10:32:56 +0200 [thread overview]
Message-ID: <20260713083256.GA4304@lst.de> (raw)
In-Reply-To: <20260713023708.9245-4-ebiggers@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-07-13 8:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 2:36 [PATCH v3 00/17] fscrypt: Standardize on blk-crypto Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 01/17] blk-crypto: Simplify check for fallback support Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 02/17] blk-crypto: Fold __blk_crypto_cfg_supported() into its caller Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 03/17] blk-crypto: Allow control over whether hardware is used Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 8:32 ` Christoph Hellwig [this message]
2026-07-13 8:32 ` Christoph Hellwig
2026-07-13 2:36 ` [PATCH v3 04/17] fscrypt: Fully disallow IV_INO_LBLK_32 with s_blocksize != PAGE_SIZE Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 05/17] fscrypt: Always use blk-crypto for contents on block-based filesystems Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 06/17] Documentation: fscrypt: Update docs for inlinecrypt Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 8:34 ` Christoph Hellwig
2026-07-13 8:34 ` [f2fs-dev] " Christoph Hellwig
2026-07-13 2:36 ` [PATCH v3 07/17] ext4: Remove fs-layer file contents en/decryption code Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:36 ` [PATCH v3 08/17] ext4: Make ext4_bio_write_folio() return void Eric Biggers
2026-07-13 2:36 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 09/17] ext4: Further de-generalize the bio postprocessing code Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 10/17] f2fs: Remove fs-layer file contents en/decryption code Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 11/17] fs/buffer: Remove fs-layer decryption code Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 12/17] fscrypt: Replace calls to fscrypt_inode_uses_inline_crypto() Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 13/17] fscrypt: Remove fscrypt_dio_supported() Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 14/17] fscrypt: Remove fs-layer zeroout code Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 15/17] fscrypt: Remove unused functions and workqueue Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 16/17] fscrypt: Merge bio.c and inline_crypt.c into block.c Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-07-13 2:37 ` [PATCH v3 17/17] fscrypt: Add safety checks to non-block-based en/decryption Eric Biggers
2026-07-13 2:37 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
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=20260713083256.GA4304@lst.de \
--to=hch@lst.de \
--cc=adilger.kernel@dilger.ca \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=libaokun@linux.alibaba.com \
--cc=linux-block@vger.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=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.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 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.