From: Greg KH <gregkh@linuxfoundation.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
peterhuewe@gmx.de, jgg@ziepe.ca, jejb@linux.ibm.com,
jarkko.sakkinen@linux.intel.com, arnd@arndb.de,
zohar@linux.ibm.com, jmorris@namei.org, serge@hallyn.com,
casey@schaufler-ca.com, ard.biesheuvel@linaro.org,
daniel.thompson@linaro.org, linux-kernel@vger.kernel.org,
tee-dev@lists.linaro.org
Subject: Re: [RFC/RFT v3 2/3] KEYS: trusted: move tpm2 trusted keys code
Date: Tue, 06 Aug 2019 13:43:22 +0000 [thread overview]
Message-ID: <20190806134322.GA10783@kroah.com> (raw)
In-Reply-To: <1565098640-12536-3-git-send-email-sumit.garg@linaro.org>
On Tue, Aug 06, 2019 at 07:07:19PM +0530, Sumit Garg wrote:
> Move TPM2 trusted keys code to trusted keys subsystem.
>
> Suggested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> drivers/char/tpm/tpm-interface.c | 56 -----
> drivers/char/tpm/tpm.h | 224 ------------------
> drivers/char/tpm/tpm2-cmd.c | 307 ------------------------
> include/keys/trusted_tpm.h | 23 +-
> include/linux/tpm.h | 264 +++++++++++++++++++--
> security/keys/trusted-keys/Makefile | 3 +-
> security/keys/trusted-keys/trusted-tpm.c | 16 +-
> security/keys/trusted-keys/trusted-tpm2.c | 378 ++++++++++++++++++++++++++++++
> 8 files changed, 652 insertions(+), 619 deletions(-)
> create mode 100644 security/keys/trusted-keys/trusted-tpm2.c
'git format-patch -M' will create a patch that shows the rename, and
then any tiny differences that happened after that. A patch like this
is hard to see what changed in the move.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
peterhuewe@gmx.de, jgg@ziepe.ca, jejb@linux.ibm.com,
jarkko.sakkinen@linux.intel.com, arnd@arndb.de,
zohar@linux.ibm.com, jmorris@namei.org, serge@hallyn.com,
casey@schaufler-ca.com, ard.biesheuvel@linaro.org,
daniel.thompson@linaro.org, linux-kernel@vger.kernel.org,
tee-dev@lists.linaro.org
Subject: Re: [RFC/RFT v3 2/3] KEYS: trusted: move tpm2 trusted keys code
Date: Tue, 6 Aug 2019 15:43:22 +0200 [thread overview]
Message-ID: <20190806134322.GA10783@kroah.com> (raw)
In-Reply-To: <1565098640-12536-3-git-send-email-sumit.garg@linaro.org>
On Tue, Aug 06, 2019 at 07:07:19PM +0530, Sumit Garg wrote:
> Move TPM2 trusted keys code to trusted keys subsystem.
>
> Suggested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> drivers/char/tpm/tpm-interface.c | 56 -----
> drivers/char/tpm/tpm.h | 224 ------------------
> drivers/char/tpm/tpm2-cmd.c | 307 ------------------------
> include/keys/trusted_tpm.h | 23 +-
> include/linux/tpm.h | 264 +++++++++++++++++++--
> security/keys/trusted-keys/Makefile | 3 +-
> security/keys/trusted-keys/trusted-tpm.c | 16 +-
> security/keys/trusted-keys/trusted-tpm2.c | 378 ++++++++++++++++++++++++++++++
> 8 files changed, 652 insertions(+), 619 deletions(-)
> create mode 100644 security/keys/trusted-keys/trusted-tpm2.c
'git format-patch -M' will create a patch that shows the rename, and
then any tiny differences that happened after that. A patch like this
is hard to see what changed in the move.
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-06 13:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 13:37 [RFC/RFT v3 0/3] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2019-08-06 13:49 ` Sumit Garg
2019-08-06 13:37 ` [RFC/RFT v3 1/3] KEYS: trusted: create trusted keys subsystem Sumit Garg
2019-08-06 13:49 ` Sumit Garg
2019-08-07 18:59 ` Jarkko Sakkinen
2019-08-07 18:59 ` Jarkko Sakkinen
2019-08-08 12:26 ` Sumit Garg
2019-08-08 12:38 ` Sumit Garg
2019-08-06 13:37 ` [RFC/RFT v3 2/3] KEYS: trusted: move tpm2 trusted keys code Sumit Garg
2019-08-06 13:49 ` Sumit Garg
2019-08-06 13:43 ` Greg KH [this message]
2019-08-06 13:43 ` Greg KH
2019-08-06 13:55 ` Sumit Garg
2019-08-06 13:55 ` Sumit Garg
2019-08-07 19:03 ` Jarkko Sakkinen
2019-08-07 19:03 ` Jarkko Sakkinen
2019-08-08 13:21 ` Sumit Garg
2019-08-08 13:33 ` Sumit Garg
2019-08-08 15:15 ` Jarkko Sakkinen
2019-08-08 15:15 ` Jarkko Sakkinen
2019-08-13 7:59 ` Sumit Garg
2019-08-13 7:59 ` Sumit Garg
2019-08-06 13:37 ` [RFC/RFT v3 3/3] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2019-08-06 13:49 ` Sumit Garg
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=20190806134322.GA10783@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--cc=tee-dev@lists.linaro.org \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.