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] tpmdd updates for Linux v6.1-rc1
Date: Wed, 5 Oct 2022 00:30:02 +0300 [thread overview]
Message-ID: <20221004213003.57166-1-jarkko@kernel.org> (raw)
Hi,
Just a few bug fixes this time.
BR, Jarkko
The following changes since commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f:
Linux 6.0 (2022-10-02 14:09:07 -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.1-rc1
for you to fetch changes up to 2d869f0b458547386fbcd8cf3004b271b7347b7f:
selftest: tpm2: Add Client.__del__() to close /dev/tpm* handle (2022-10-05 00:25:56 +0300)
----------------------------------------------------------------
tpmdd updates for Linux v6.1-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-10-04 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 21:30 Jarkko Sakkinen [this message]
2022-10-10 20:56 ` [GIT PULL] tpmdd updates for Linux v6.1-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=20221004213003.57166-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 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.