[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190801172310.cldcftfdoh5vyfjg@linux.intel.com>
Date: Thu, 1 Aug 2019 20:24:15 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: keyrings@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-crypto@...r.kernel.org,
linux-security-module@...r.kernel.org, dhowells@...hat.com,
herbert@...dor.apana.org.au, davem@...emloft.net,
jejb@...ux.ibm.com, zohar@...ux.ibm.com, jmorris@...ei.org,
serge@...lyn.com, casey@...aufler-ca.com,
ard.biesheuvel@...aro.org, daniel.thompson@...aro.org,
linux-kernel@...r.kernel.org, tee-dev@...ts.linaro.org
Subject: Re: [RFC/RFT v2 1/2] KEYS: trusted: create trusted keys subsystem
On Thu, Jul 18, 2019 at 04:54:45PM +0530, Sumit Garg wrote:
> Move existing code to trusted keys subsystem. Also, rename files with
> "tpm" as suffix which provides the underlying implementation.
>
> Suggested-by: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@...aro.org>
What about TPM2 trusted keys code?
/Jarkko
Powered by blists - more mailing lists