linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
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,
	arnd@arndb.de, gregkh@linuxfoundation.org, 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: [PATCH v5 0/4] Create and consolidate trusted keys subsystem
Date: Wed, 21 Aug 2019 22:20:35 +0300	[thread overview]
Message-ID: <20190821192035.aahtxb3qyl4vpezv@linux.intel.com> (raw)
In-Reply-To: <1566392345-15419-1-git-send-email-sumit.garg@linaro.org>

On Wed, Aug 21, 2019 at 06:29:01PM +0530, Sumit Garg wrote:
> [SNIP]

Thank you. And as I promised I will give my remarks about 5/5 in the
previous revision.

/Jarkko

      parent reply	other threads:[~2019-08-21 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 12:59 [PATCH v5 0/4] Create and consolidate trusted keys subsystem Sumit Garg
2019-08-21 12:59 ` [PATCH v5 1/4] tpm: move tpm_buf code to include/linux/ Sumit Garg
2019-08-27 13:48   ` Jarkko Sakkinen
2019-08-21 12:59 ` [PATCH v5 2/4] KEYS: trusted: use common tpm_buf for TPM1.x code Sumit Garg
2019-08-21 12:59 ` [PATCH v5 3/4] KEYS: trusted: create trusted keys subsystem Sumit Garg
2019-08-27 13:48   ` Jarkko Sakkinen
2019-08-21 12:59 ` [PATCH v5 4/4] KEYS: trusted: move tpm2 trusted keys code Sumit Garg
2019-08-27 14:17   ` Jarkko Sakkinen
2019-08-28  5:28     ` Sumit Garg
2019-08-29 14:53       ` Jarkko Sakkinen
2019-08-21 19:20 ` Jarkko Sakkinen [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=20190821192035.aahtxb3qyl4vpezv@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --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=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).