From: Eric Biggers <ebiggers@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
linux-fscrypt@vger.kernel.org, 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,
Gaurav Kashyap <quic_gaurkash@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Jens Axboe <axboe@kernel.dk>,
Konrad Dybcio <konradybcio@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH v12 0/4] Driver and fscrypt support for HW-wrapped inline encryption keys
Date: Mon, 10 Mar 2025 09:41:58 -0700 [thread overview]
Message-ID: <20250310164158.GA1701@sol.localdomain> (raw)
In-Reply-To: <20250302222336.GD2079@quark.localdomain>
On Sun, Mar 02, 2025 at 02:23:36PM -0800, Eric Biggers wrote:
> > > TBD whether these will land in 6.15 too, or wait until 6.16 when the
> > > block patches that patches 2-4 depend on will have landed.
> > >
> >
> > Could Jens provide an immutable branch with these patches? I don't
> > think there's a reason to delay it for another 3 months TBH.
>
> They don't seem to be on an immutable branch, so I'll just wait until the next
> cycle, rather than trying to do something weird where I rebase the fscrypt tree
> onto the block tree and also include driver patches. TBH, I've already been
> waiting 5 years to land this, so an extra 9 weeks is not a big deal :-)
>
> The first patch "soc: qcom: ice: make qcom_ice_program_key() take struct
> blk_crypto_key" does not depend on the block ones though, and it could land in
> 6.15. Bjorn, would you like to take that patch through your tree to get it out
> of the way?
Bjorn, could you apply patch 1 to your tree? Thanks!
- Eric
prev parent reply other threads:[~2025-03-10 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 20:23 [PATCH v12 0/4] Driver and fscrypt support for HW-wrapped inline encryption keys Eric Biggers
2025-02-10 20:23 ` [PATCH v12 1/4] soc: qcom: ice: make qcom_ice_program_key() take struct blk_crypto_key Eric Biggers
2025-02-10 20:23 ` [PATCH v12 2/4] soc: qcom: ice: add HWKM support to the ICE driver Eric Biggers
2025-02-10 20:23 ` [PATCH v12 3/4] ufs: qcom: add support for wrapped keys Eric Biggers
2025-02-10 20:23 ` [PATCH v12 4/4] fscrypt: add support for hardware-wrapped keys Eric Biggers
2025-02-11 8:12 ` [PATCH v12 0/4] Driver and fscrypt support for HW-wrapped inline encryption keys Bartosz Golaszewski
2025-03-02 22:23 ` Eric Biggers
2025-03-10 16:41 ` Eric Biggers [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=20250310164158.GA1701@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