From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [GIT PULL] linux-tpmdd updates for v6.0-rc1
Date: Wed, 28 Sep 2022 03:58:52 +0300 [thread overview]
Message-ID: <20220928005852.10729-1-jarkko@kernel.org> (raw)
Hi,
Just some bug fixes.
BR, Jarkko
The following changes since commit f76349cf41451c5c42a99f18a9163377e4b364ff:
Linux 6.0-rc7 (2022-09-25 14:01:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/ tags/tpmdd-next-v6.0-rc1
for you to fetch changes up to 603fd3d42e144ca36e8340c81b0144c5e7f8b9c2:
selftest: tpm2: Add Client.__del__() to close /dev/tpm* handle (2022-09-28 03:53:47 +0300)
----------------------------------------------------------------
tpmdd updates for Linux v6.0-rc1
----------------------------------------------------------------
Stefan Berger (1):
selftest: tpm2: Add Client.__del__() to close /dev/tpm* handle
Vincenzo Frascino (1):
security/keys: Remove inconsistent __user annotation
Wolfram Sang (1):
char: move from strlcpy with unused retval to strscpy
drivers/char/tpm/tpm_ppi.c | 2 +-
security/keys/keyring.c | 2 +-
tools/testing/selftests/tpm2/tpm2.py | 4 ++++
3 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2022-09-28 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 0:58 Jarkko Sakkinen [this message]
2022-09-28 2:32 ` [GIT PULL] linux-tpmdd updates for v6.0-rc1 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=20220928005852.10729-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--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 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).