From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
jmorris@namei.org
Subject: [GIT PULL] tpmdd fixes for Linux v5.4-rc1
Date: Wed, 25 Sep 2019 03:02:14 +0300 [thread overview]
Message-ID: <20190925000214.GA23372@linux.intel.com> (raw)
Hi
These are bug fixes for bugs found after my v5.4 PR.
/Jarkko
The following changes since commit 4c07e2ddab5b6b57dbcb09aedbda1f484d5940cc:
Merge tag 'mfd-next-5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd (2019-09-23 19:37:49 -0700)
are available in the Git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20190925
for you to fetch changes up to e13cd21ffd50a07b55dcc4d8c38cedf27f28eaa1:
tpm: Wrap the buffer from the caller to tpm_buf in tpm_send() (2019-09-25 02:43:57 +0300)
----------------------------------------------------------------
tpmdd fixes for Linux v5.4
----------------------------------------------------------------
Denis Efremov (1):
MAINTAINERS: keys: Update path to trusted.h
Jarkko Sakkinen (2):
selftests/tpm2: Add the missing TEST_FILES assignment
tpm: Wrap the buffer from the caller to tpm_buf in tpm_send()
Petr Vorel (1):
selftests/tpm2: Add log and *.pyc to .gitignore
Roberto Sassu (1):
KEYS: trusted: correctly initialize digests and fix locking issue
MAINTAINERS | 2 +-
drivers/char/tpm/tpm-interface.c | 23 +++++++++++------------
security/keys/trusted.c | 5 +++++
tools/testing/selftests/.gitignore | 2 ++
tools/testing/selftests/tpm2/Makefile | 1 +
5 files changed, 20 insertions(+), 13 deletions(-)
next reply other threads:[~2019-09-25 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 0:02 Jarkko Sakkinen [this message]
2019-09-25 17:40 ` [GIT PULL] tpmdd fixes for Linux v5.4-rc1 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=20190925000214.GA23372@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=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.