All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: David Howells <dhowells@redhat.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	peterhuewe@gmx.de, gregkh@linuxfoundation.org,
	jgunthorpe@obsidianresearch.com,
	"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>,
	"open list:KEYS-TRUSTED" <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Basic trusted keys support for TPM 2.0
Date: Fri, 16 Oct 2015 21:30:49 +0300	[thread overview]
Message-ID: <20151016183049.GB6368@intel.com> (raw)
In-Reply-To: <30615.1445012462@warthog.procyon.org.uk>

Hi

On Fri, Oct 16, 2015 at 05:21:02PM +0100, David Howells wrote:
> Hi Jarkko,
> 
> For some reason I don't see patch 1.

Weird. Well, maybe the best way to proceed is that I'll send the
contents of for-peter-v44 branch for review. It's 9 patches in total,
PPI, trusted keys and couple of bug fixes.

> David

/Jarkko

      reply	other threads:[~2015-10-16 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  8:11 [PATCH v2 0/4] Basic trusted keys support for TPM 2.0 Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 1/4] tpm: introduce tpm_buf Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 2/4] keys, trusted: move struct trusted_key_options to trusted-type.h Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 3/4] tpm: seal/unseal for TPM 2.0 Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 4/4] keys, trusted: seal/unseal with TPM 2.0 chips Jarkko Sakkinen
2015-10-13  8:53 ` [PATCH v2 0/4] Basic trusted keys support for TPM 2.0 Jarkko Sakkinen
2015-10-13 17:41 ` Jason Gunthorpe
2015-10-13 19:25   ` Jarkko Sakkinen
2015-10-16 16:21 ` David Howells
2015-10-16 18:30   ` 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=20151016183049.GB6368@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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.