From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gaurav Kashyap <quic_gaurkash@quicinc.com>,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
ebiggers@google.com, neil.armstrong@linaro.org,
srinivas.kandagatla@linaro.org
Cc: linux-mmc@vger.kernel.org, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org, omprsing@qti.qualcomm.com,
quic_psodagud@quicinc.com, abel.vesa@linaro.org,
quic_spuppala@quicinc.com, kernel@quicinc.com
Subject: Re: [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs
Date: Wed, 22 Nov 2023 10:55:40 +0100 [thread overview]
Message-ID: <808e5f24-0366-4071-bf97-93611d4ced08@kernel.org> (raw)
In-Reply-To: <20231122053817.3401748-1-quic_gaurkash@quicinc.com>
On 22/11/2023 06:38, Gaurav Kashyap wrote:
> ice, ufs, mmc: use blk_crypto_key for program_key
> qcom_scm: scm call for deriving a software secret
> soc: qcom: ice: add hwkm support in ice
> soc: qcom: ice: support for hardware wrapped keys
> ufs: core: support wrapped keys in ufs core
> ufs: host: wrapped keys support in ufs qcom
> qcom_scm: scm call for create, prepare and import keys
> ufs: core: add support for generate, import and prepare keys
> soc: qcom: support for generate, import and prepare key
> ufs: host: support for generate, import and prepare key
> arm64: dts: qcom: sm8650: add hwkm support to ufs ice
This is close to a spaghetti patchset. ICE, UFS, MMC, then followed up
by SoC patches, then UFS, then firmware, then UFS, then again SoC and we
are back at UFS.
Crazy dependencies... or you collected unrelated patches into one
patchset making the merge strategy tricky.
> dt-bindings: crypto: ice: document the hwkm property
Bindings come before users.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-22 9:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 5:38 [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs Gaurav Kashyap
2023-11-22 5:38 ` [PATCH v3 01/12] ice, ufs, mmc: use blk_crypto_key for program_key Gaurav Kashyap
2023-12-08 6:22 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 02/12] qcom_scm: scm call for deriving a software secret Gaurav Kashyap
2023-11-22 17:43 ` Trilok Soni
2023-12-08 6:38 ` Om Prakash Singh
2023-12-12 4:09 ` Gaurav Kashyap
2023-11-22 5:38 ` [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice Gaurav Kashyap
2023-12-08 4:11 ` Bjorn Andersson
2023-12-12 3:53 ` Gaurav Kashyap
2023-12-08 6:04 ` Om Prakash Singh
2023-12-12 3:58 ` Gaurav Kashyap
2023-12-08 6:06 ` Om Prakash Singh
2023-12-08 6:11 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 04/12] soc: qcom: ice: support for hardware wrapped keys Gaurav Kashyap
2023-12-08 7:45 ` Om Prakash Singh
2023-12-12 4:04 ` Gaurav Kashyap
2023-11-22 5:38 ` [PATCH v3 05/12] ufs: core: support wrapped keys in ufs core Gaurav Kashyap
2023-12-08 3:42 ` Bjorn Andersson
2023-11-22 5:38 ` [PATCH v3 06/12] ufs: host: wrapped keys support in ufs qcom Gaurav Kashyap
2023-12-08 7:54 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 07/12] qcom_scm: scm call for create, prepare and import keys Gaurav Kashyap
2023-12-13 8:11 ` Mukesh Ojha
2023-11-22 5:38 ` [PATCH v3 08/12] ufs: core: add support for generate, import and prepare keys Gaurav Kashyap
2023-12-08 3:49 ` Bjorn Andersson
2023-12-08 8:17 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 09/12] soc: qcom: support for generate, import and prepare key Gaurav Kashyap
2023-12-08 8:26 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 10/12] ufs: host: " Gaurav Kashyap
2023-12-08 8:29 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 11/12] arm64: dts: qcom: sm8650: add hwkm support to ufs ice Gaurav Kashyap
2023-12-08 3:51 ` Bjorn Andersson
2023-12-08 8:45 ` Om Prakash Singh
2023-12-08 8:46 ` Om Prakash Singh
2023-11-22 5:38 ` [PATCH v3 12/12] dt-bindings: crypto: ice: document the hwkm property Gaurav Kashyap
2023-11-22 9:53 ` Krzysztof Kozlowski
2023-12-08 4:16 ` Bjorn Andersson
2023-11-22 9:55 ` Krzysztof Kozlowski [this message]
2023-12-05 17:33 ` [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs neil.armstrong
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=808e5f24-0366-4071-bf97-93611d4ced08@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=ebiggers@google.com \
--cc=kernel@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=omprsing@qti.qualcomm.com \
--cc=quic_gaurkash@quicinc.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_spuppala@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
/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