From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.19-rc1-v3
Date: Wed, 3 Dec 2025 04:02:00 +0200 [thread overview]
Message-ID: <aS-aGEmiCks9EY30@kernel.org> (raw)
In-Reply-To: <aS4m3QWXzE4nSG1O@kernel.org>
On Tue, Dec 02, 2025 at 01:38:05AM +0200, Jarkko Sakkinen wrote:
> The following changes since commit 4664fb427c8fd0080f40109f5e2b2090a6fb0c84:
>
> Merge tag 'vfs-6.19-rc1.minix' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs (2025-12-01 15:22:40 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-next-6.19-rc1-v3
>
> for you to fetch changes up to b8b93e380604ce33e41e78522406df011f07aefe:
>
> KEYS: trusted: Use tpm_ret_to_err() in trusted_tpm2 (2025-12-02 01:30:23 +0200)
>
> ----------------------------------------------------------------
> Hi,
>
> This pull request for TPM driver contains changes to unify TPM return
> code translation between trusted_tpm2 and TPM driver itself. Other than
> that the changes are either bug fixes or minor imrovements.
>
> Removed commits from earlier revisions and associated lore links:
>
> 1. "drivers/char/tpm: use min() instead of min_t()"
> https://lore.kernel.org/all/20251201161228.3c09d88a@pumpkin/
> 2. "Documentation: tpm-security.rst: change title to section"
> https://lore.kernel.org/all/86514a6ab364e01f163470a91cacef120e1b8b47.camel@HansenPartnership.com/
>
> BR, Jarkko
>
> ----------------------------------------------------------------
> Chu Guangqing (1):
> tpm_crb: Fix a spelling mistake
>
> Jarkko Sakkinen (3):
> tpm: Cap the number of PCR banks
> tpm: Use -EPERM as fallback error code in tpm_ret_to_err
> KEYS: trusted: Use tpm_ret_to_err() in trusted_tpm2
>
> Jonathan McDowell (1):
> tpm: Remove tpm_find_get_ops
>
> Marco Crivellari (1):
> tpm: add WQ_PERCPU to alloc_workqueue users
>
> Maurice Hieronymus (1):
> selftests: tpm2: Fix ill defined assertions
>
> Stuart Yoder (1):
> tpm_crb: add missing loc parameter to kerneldoc
>
> drivers/char/tpm/tpm-chip.c | 36 -------------------------------
> drivers/char/tpm/tpm-dev-common.c | 3 ++-
> drivers/char/tpm/tpm-interface.c | 20 +++++++++++++----
> drivers/char/tpm/tpm.h | 1 -
> drivers/char/tpm/tpm1-cmd.c | 5 -----
> drivers/char/tpm/tpm2-cmd.c | 8 +++----
> drivers/char/tpm/tpm_crb.c | 4 +++-
> drivers/char/tpm/tpm_tis_core.c | 3 +--
> include/linux/tpm.h | 12 +++++++----
> security/keys/trusted-keys/trusted_tpm2.c | 26 ++++++----------------
> tools/testing/selftests/tpm2/tpm2.py | 4 ++--
> 11 files changed, 42 insertions(+), 80 deletions(-)
This is getting silly but I'll update this one more time.
BR, Jarkkok
prev parent reply other threads:[~2025-12-03 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 23:38 [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.19-rc1-v3 Jarkko Sakkinen
2025-12-03 2:02 ` Jarkko Sakkinen [this message]
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=aS-aGEmiCks9EY30@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--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