From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] tpmdd fixes for Linux 4.8
Date: Fri, 02 Sep 2016 12:29:40 +0300 [thread overview]
Message-ID: <1472808580.7142.16.camel@linux.intel.com> (raw)
[I recreated the tag and resent this because I forgot to add Reviewed-by]
Hi
I decided to make one more pull request for 4.8. This contains only the
fix for the invalid self test message that occurs when the driver
initialiazes a TPM 2.0 chip.
I don't mind if this is postponed after 4.8 is released because this is
only a glitch and does not break semantics but I just thought since it's
such a small scoped change that I anyway make a pull request available.
/Jarkko
The following changes since commit 8ccc7d6bad84bebf1f1a6364d1fa04d3d7b575f6:
seccomp: Remove 2-phase API documentation (2016-08-09 11:07:05 +1000)
are available in the git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20160902
for you to fetch changes up to 289979f5ad937e684b65416223a8c35f21072068:
tpm: invalid self test error message (2016-09-02 12:11:29 +0300)
----------------------------------------------------------------
tpmdd fixes for Linux 4.8
----------------------------------------------------------------
Jarkko Sakkinen (1):
tpm: invalid self test error message
drivers/char/tpm/tpm2-cmd.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
next reply other threads:[~2016-09-02 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:29 Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-02 8:05 [GIT PULL] tpmdd fixes for Linux 4.8 Jarkko Sakkinen
2016-07-19 14:53 Jarkko Sakkinen
2016-07-20 5:58 ` James Morris
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=1472808580.7142.16.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.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 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.