From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
Gaurav Kashyap <quic_gaurkash@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Jens Axboe <axboe@kernel.dk>,
Konrad Dybcio <konradybcio@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH v13 0/3] Support for wrapped inline encryption keys on Qualcomm SoCs
Date: Fri, 11 Apr 2025 21:17:57 -0400 [thread overview]
Message-ID: <yq1ecxyjhzd.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250404231533.174419-1-ebiggers@kernel.org> (Eric Biggers's message of "Fri, 4 Apr 2025 16:15:29 -0700")
Eric,
> Add support for hardware-wrapped inline encryption keys to the
> Qualcomm ICE (Inline Crypto Engine) and UFS (Universal Flash Storage)
> drivers.
>
> I'd like these patches to be taken through the scsi tree for 6.16.
Applied to 6.16/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2025-04-12 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 23:15 [PATCH v13 0/3] Support for wrapped inline encryption keys on Qualcomm SoCs Eric Biggers
2025-04-04 23:15 ` [PATCH v13 1/3] soc: qcom: ice: make qcom_ice_program_key() take struct blk_crypto_key Eric Biggers
2025-04-07 8:43 ` Konrad Dybcio
2025-04-04 23:15 ` [PATCH v13 2/3] soc: qcom: ice: add HWKM support to the ICE driver Eric Biggers
2025-04-04 23:15 ` [PATCH v13 3/3] ufs: qcom: add support for wrapped keys Eric Biggers
2025-04-08 12:54 ` [PATCH v13 0/3] Support for wrapped inline encryption keys on Qualcomm SoCs Ulf Hansson
2025-04-12 1:17 ` Martin K. Petersen [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=yq1ecxyjhzd.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=andersson@kernel.org \
--cc=axboe@kernel.dk \
--cc=brgl@bgdev.pl \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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