From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas =?ISO-8859-1?Q?Wei=DFschuh?= <linux@weissschuh.net>,
"Matthew Garrett" <mgarrett@aurora.tech>,
Uwe =?ISO-8859-1?Q?Kleine-K=F6nig?=
<u.kleine-koenig@pengutronix.de>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] tpm: changes for v6.3-rc4
Date: Mon, 20 Mar 2023 15:37:18 +0200 [thread overview]
Message-ID: <20230320133718.m2z4kal4nxhofvbx@kernel.org> (raw)
Hi,
Sent because of a build fix for previous PR. Also couple of less important
fixes.
BR, Jarkko
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpm-v6.3-rc4
for you to fetch changes up to 923c8dfa9a3640d4dcedd7df12b53254f7e6e4fc:
tpm: fix build break in tpm-chip.c caused by AMD fTPM quirk (2023-03-20 15:27:03 +0200)
----------------------------------------------------------------
tpm: v6.3-rc4
----------------------------------------------------------------
James Bottomley (1):
tpm: fix build break in tpm-chip.c caused by AMD fTPM quirk
Mark Hasemeyer (1):
tpm: cr50: i2c: use jiffies to wait for tpm ready irq
Yu Zhe (1):
tpm: remove unnecessary (void*) conversions
drivers/char/tpm/eventlog/common.c | 6 +++---
drivers/char/tpm/tpm-chip.c | 2 +-
drivers/char/tpm/tpm_tis_i2c_cr50.c | 3 +--
3 files changed, 5 insertions(+), 6 deletions(-)
next reply other threads:[~2023-03-20 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 13:37 Jarkko Sakkinen [this message]
2023-03-20 13:40 ` [GIT PULL] tpm: changes for v6.3-rc4 Jarkko Sakkinen
2023-03-20 13:42 ` 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=20230320133718.m2z4kal4nxhofvbx@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mgarrett@aurora.tech \
--cc=peterhuewe@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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