From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <james.l.morris@oracle.com>
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for v4.16
Date: Wed, 10 Jan 2018 18:18:30 +0200 [thread overview]
Message-ID: <20180110161830.kh5zlatbtiebzkbh@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1801091141410.17337@localhost>
On Tue, Jan 09, 2018 at 11:42:16AM +1100, James Morris wrote:
> On Mon, 8 Jan 2018, Jarkko Sakkinen wrote:
>
> > Hi James,
> >
> > Sorry for a late PR.
> >
> > Summary of the content:
> >
> > * Reduced polling delays in tpm_tis.
> > * Support for retrieving TPM 2.0 Event Log through EFI before
> > ExitBootServices.
> > * Replaced tpm-rng.c with a hwrng device managed by the driver for each
> > TPM device.
> > * TPM resource manager synthesizes TPM_RC_COMMAND_CODE response instead
> > of returning -EINVAL for unknown TPM commands. This makes user space
> > more sound.
> > * CLKRUN fixes:
> > * Keep #CLKRUN disable through the entier TPM command/response flow.
> > * Check whether #CLKRUN is enabled before disabling and enabling it
> > again because enabling it breaks PS/2 devices on a system where it
> > is disabled.
> >
>
> Thanks, merged to:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
> next-tpm
> next-testing
Thank you. We'll follow the issues that Alexander described.
/Jarkko
next prev parent reply other threads:[~2018-01-10 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 11:18 [GIT PULL] tpmdd updates for v4.16 Jarkko Sakkinen
2018-01-09 0:42 ` James Morris
2018-01-10 16:18 ` Jarkko Sakkinen [this message]
2018-01-09 9:59 ` Alexander Steffen
2018-01-10 16:08 ` Jarkko Sakkinen
2018-01-11 17:29 ` Alexander Steffen
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=20180110161830.kh5zlatbtiebzkbh@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=james.l.morris@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--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