All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-integrity@vger.kernel.org, jmorris@namei.org
Subject: Re: [GIT PULL] tpmdd updates for Linux v5.5
Date: Thu, 14 Nov 2019 18:41:07 +0200	[thread overview]
Message-ID: <20191114164047.GA9528@linux.intel.com> (raw)
In-Reply-To: <20191112195826.GA5584@ziepe.ca>

On Tue, Nov 12, 2019 at 03:58:26PM -0400, Jason Gunthorpe wrote:
> On Tue, Nov 12, 2019 at 09:55:42PM +0200, Jarkko Sakkinen wrote:
> > 1. Support for Cr50 fTPM.
> > 2. Support for fTPM on AMD Zen+ CPUs.
> > 3. TPM 2.0 trusted keys code relocated from drivers/char/tpm to
> >    security/keys.
> 
> Just to be clear, this is for the next merge window right?

v5.5-rc1

/Jarkko

  reply	other threads:[~2019-11-14 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 19:55 [GIT PULL] tpmdd updates for Linux v5.5 Jarkko Sakkinen
2019-11-12 19:58 ` Jason Gunthorpe
2019-11-14 16:41   ` Jarkko Sakkinen [this message]
2019-11-25 22:45 ` pr-tracker-bot

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=20191114164047.GA9528@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=jmorris@namei.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.