From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: jmorris@namei.org
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] tpmdd updates for Linux 4.17
Date: Fri, 23 Mar 2018 11:33:12 +0200 [thread overview]
Message-ID: <20180323093312.GA21411@linux.intel.com> (raw)
Hi James
This release contains only bug fixes. There are no new major features
added.
/Jarkko
The following changes since commit 5893ed18a26d1f56b97c0290b0cbbc2d49d6de28:
Merge tag 'v4.16-rc6' into next-general (2018-03-23 08:26:16 +1100)
are available in the Git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20180323
for you to fetch changes up to 2be8ffed093b91536d52b5cd2c99b52f605c9ba6:
tpm: fix intermittent failure with self tests (2018-03-23 10:25:09 +0200)
----------------------------------------------------------------
tpmdd updates for Linux 4.17
----------------------------------------------------------------
Chris Chiu (1):
tpm: self test failure should not cause suspend to fail
James Bottomley (2):
tpm: add retry logic
tpm: fix intermittent failure with self tests
Tomas Winkler (3):
tpm: cmd_ready command can be issued only after granting locality
tpm_crb: use __le64 annotated variable for response buffer address
tpm2: add longer timeouts for creation commands.
Winkler, Tomas (2):
tpm: tpm-interface: fix tpm_transmit/_cmd kdoc
tpm: fix buffer type in tpm_transmit_cmd
drivers/char/tpm/tpm-interface.c | 158 +++++++++++++++++++++++++++++++--------
drivers/char/tpm/tpm.h | 32 +++++---
drivers/char/tpm/tpm2-cmd.c | 62 ++++++---------
drivers/char/tpm/tpm_crb.c | 113 +++++++++++++++++++---------
drivers/char/tpm/tpm_tis_core.c | 4 +-
include/linux/tpm.h | 2 +-
6 files changed, 250 insertions(+), 121 deletions(-)
next reply other threads:[~2018-03-23 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 9:33 Jarkko Sakkinen [this message]
2018-03-23 20:52 ` [GIT PULL] tpmdd updates for Linux 4.17 James Morris
2018-03-26 13:40 ` Jarkko Sakkinen
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=20180323093312.GA21411@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.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;
as well as URLs for NNTP newsgroup(s).