linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for Linux v4.21
Date: Tue, 18 Dec 2018 06:33:03 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1812180632420.29218@namei.org> (raw)
In-Reply-To: <20181217132033.GA31729@linux.intel.com>

On Mon, 17 Dec 2018, Jarkko Sakkinen wrote:

> Hi James,
> 
> v4.21 updates:
> 
> * Support for partial reads of /dev/tpm0.
> * Clean up for TPM 1.x code: move the commands to tpm1-cmd.c and make
>   everything to use the same data structure for building TPM commands
>   i.e. struct tpm_buf.

Pulled to next-tpm and next-testing.

-- 
James Morris
<jmorris@namei.org>


      reply	other threads:[~2018-12-17 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 13:20 [GIT PULL] tpmdd updates for Linux v4.21 Jarkko Sakkinen
2018-12-17 19:33 ` James Morris [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=alpine.LRH.2.21.1812180632420.29218@namei.org \
    --to=jmorris@namei.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    /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).