From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
Gaurav Kashyap <quic_gaurkash@quicinc.com>,
Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: (subset) [PATCH v11 0/7] Support for hardware-wrapped inline encryption keys
Date: Mon, 10 Feb 2025 09:54:55 -0700 [thread overview]
Message-ID: <173920649542.40307.8847368467858129326.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250204060041.409950-1-ebiggers@kernel.org>
On Mon, 03 Feb 2025 22:00:34 -0800, Eric Biggers wrote:
> This patchset is based on v6.14-rc1 and is also available at:
>
> git fetch https://git.kernel.org/pub/scm/fs/fscrypt/linux.git wrapped-keys-v11
>
> This patchset adds support for hardware-wrapped inline encryption keys,
> a security feature supported by some SoCs. It adds the block and
> fscrypt framework for the feature as well as support for it with UFS on
> Qualcomm SoCs.
>
> [...]
Applied, thanks!
[1/7] blk-crypto: add basic hardware-wrapped key support
commit: ebc4176551cdd021d02f4d2ed734e7b65e44442a
[2/7] blk-crypto: show supported key types in sysfs
commit: e35fde43e25ad725d27315992fba8088d1210b01
[3/7] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
commit: 1ebd4a3c095cd538d3c1c7c12738ef47d8e71f96
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-10 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 6:00 [PATCH v11 0/7] Support for hardware-wrapped inline encryption keys Eric Biggers
2025-02-04 6:00 ` [PATCH v11 1/7] blk-crypto: add basic hardware-wrapped key support Eric Biggers
2025-02-04 6:00 ` [PATCH v11 2/7] blk-crypto: show supported key types in sysfs Eric Biggers
2025-02-04 6:00 ` [PATCH v11 3/7] blk-crypto: add ioctls to create and prepare hardware-wrapped keys Eric Biggers
2025-02-04 6:00 ` [PATCH v11 4/7] fscrypt: add support for " Eric Biggers
2025-02-04 6:00 ` [PATCH v11 5/7] soc: qcom: ice: make qcom_ice_program_key() take struct blk_crypto_key Eric Biggers
2025-02-09 15:50 ` Manivannan Sadhasivam
2025-02-04 6:00 ` [PATCH v11 6/7] soc: qcom: ice: add HWKM support to the ICE driver Eric Biggers
2025-02-08 20:01 ` kernel test robot
2025-02-04 6:00 ` [PATCH v11 7/7] ufs: qcom: add support for wrapped keys Eric Biggers
2025-02-10 4:44 ` Manivannan Sadhasivam
2025-02-10 16:21 ` Eric Biggers
2025-02-04 10:42 ` [PATCH v11 0/7] Support for hardware-wrapped inline encryption keys Bartosz Golaszewski
2025-02-10 16:25 ` Eric Biggers
2025-02-10 16:54 ` Jens Axboe [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=173920649542.40307.8847368467858129326.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=dmitry.baryshkov@linaro.org \
--cc=ebiggers@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_gaurkash@quicinc.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