[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190819170635.jlxxi6ogbm4s6gcx@linux.intel.com>
Date: Mon, 19 Aug 2019 20:06:35 +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,
peterhuewe@....de, jgg@...pe.ca, jejb@...ux.ibm.com, arnd@...db.de,
gregkh@...uxfoundation.org, 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 v4 3/5] KEYS: trusted: create trusted keys subsystem
On Mon, Aug 19, 2019 at 08:04:58PM +0300, Jarkko Sakkinen wrote:
> On Tue, Aug 13, 2019 at 01:23:02PM +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>
> > ---
> > crypto/asymmetric_keys/asym_tpm.c | 2 +-
> > include/keys/{trusted.h => trusted_tpm.h} | 4 ++--
> > security/keys/Makefile | 2 +-
> > security/keys/trusted-keys/Makefile | 7 +++++++
> > security/keys/{trusted.c => trusted-keys/trusted-tpm.c} | 2 +-
> > 5 files changed, 12 insertions(+), 5 deletions(-)
> > rename include/keys/{trusted.h => trusted_tpm.h} (98%)
> > create mode 100644 security/keys/trusted-keys/Makefile
> > rename security/keys/{trusted.c => trusted-keys/trusted-tpm.c} (99%)
>
> Would prefer trusted_tpm.c.
Actually, trusted_tpm1.c.
/Jarkko
Powered by blists - more mailing lists