From: Eric Biggers <ebiggers@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
Gaurav Kashyap <quic_gaurkash@quicinc.com>,
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: [PATCH v11 0/7] Support for hardware-wrapped inline encryption keys
Date: Mon, 10 Feb 2025 08:25:07 -0800 [thread overview]
Message-ID: <20250210162507.GB1264@sol.localdomain> (raw)
In-Reply-To: <20250204060041.409950-1-ebiggers@kernel.org>
Hi Jens,
On Mon, Feb 03, 2025 at 10:00:34PM -0800, Eric Biggers wrote:
> This is targeting 6.15. As per the suggestion from Jens
> (https://lore.kernel.org/linux-block/c3407d1c-6c5c-42ee-b446-ccbab1643a62@kernel.dk/),
> I'd like patches 1-3 to be queued up into a branch that gets pulled into
> the block tree. I'll then take patches 4-7 through the fscrypt tree,
> also for 6.15. If I end up with too many merge conflicts by trying to
> take patches 5-7 (given that this is a cross-subsystem feature), my
> fallback plan will be to wait until 6.16 to land patches 5-7, when they
> will finally be unblocked by the block patches having landed.
Let me know what you think about this plan.
- Eric
next prev parent reply other threads:[~2025-02-10 16:25 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 [this message]
2025-02-10 16:54 ` (subset) " Jens Axboe
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=20250210162507.GB1264@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=andersson@kernel.org \
--cc=axboe@kernel.dk \
--cc=brgl@bgdev.pl \
--cc=dmitry.baryshkov@linaro.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