[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <215bc107-aa47-62bd-65ad-f76e65ee75d5@intel.com>
Date: Thu, 13 Jan 2022 14:16:12 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Chang S. Bae" <chang.seok.bae@...el.com>,
linux-crypto@...r.kernel.org, dm-devel@...hat.com,
herbert@...dor.apana.org.au, ebiggers@...nel.org, ardb@...nel.org,
x86@...nel.org, luto@...nel.org, tglx@...utronix.de, bp@...e.de,
dave.hansen@...ux.intel.com, mingo@...nel.org
Cc: linux-kernel@...r.kernel.org, dan.j.williams@...el.com,
charishma1.gairuboyina@...el.com, kumar.n.dwarakanath@...el.com,
ravi.v.shankar@...el.com
Subject: Re: [PATCH v5 00/12] x86: Support Key Locker
On 1/12/22 1:12 PM, Chang S. Bae wrote:
> A couple of other things outside of these patches are still in progress:
> * Support DM-crypt/cryptsetup for Key Locker usage (Andy Lutomirski)
> [2].
> * Understand decryption under-performance (Eric Biggers and Milan Broz)
> [3][4].
I really like when contributors are clear about why they are posting
their series and what their expectations are. This posting leaves me a
bit confused as to what you expect the maintainers to do.
Should the maintainers ignore this series until those in-progress things
are done? Or, do you expect that this could be merged as-is before
those are resolved?
Powered by blists - more mailing lists