public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.19-rc1
Date: Fri, 28 Nov 2025 00:26:04 +0200	[thread overview]
Message-ID: <aSjP_BsakvhxSDYR@kernel.org> (raw)

The following changes since commit e1afacb68573c3cd0a3785c6b0508876cd3423bc:

  Merge tag 'ceph-for-6.18-rc8' of https://github.com/ceph/ceph-client (2025-11-27 11:11:03 -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

for you to fetch changes up to 35ef1e24392ff0f3b28654b452f9720f07e9533f:

  KEYS: trusted: Use tpm_ret_to_err() in trusted_tpm2 (2025-11-28 00:17:26 +0200)

----------------------------------------------------------------
Hi

The first 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 small adjustments.

BR, Jarkko

----------------------------------------------------------------
Bagas Sanjaya (1):
      Documentation: tpm-security.rst: change title to section heading

Chu Guangqing (1):
      tpm_crb: Fix a spelling mistake

David Laight (1):
      drivers/char/tpm: use min() instead of min_t()

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

 Documentation/security/tpm/tpm-security.rst |  2 +-
 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                 |  7 +-----
 drivers/char/tpm/tpm2-cmd.c                 |  8 +++----
 drivers/char/tpm/tpm_crb.c                  |  4 +++-
 drivers/char/tpm/tpm_tis_core.c             |  7 +++---
 include/linux/tpm.h                         | 12 ++++++----
 security/keys/trusted-keys/trusted_tpm2.c   | 26 ++++++---------------
 tools/testing/selftests/tpm2/tpm2.py        |  4 ++--
 12 files changed, 46 insertions(+), 84 deletions(-)

             reply	other threads:[~2025-11-27 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 22:26 Jarkko Sakkinen [this message]
2025-11-28  4:18 ` [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.19-rc1 James Bottomley
2025-11-28 15:04   ` Jarkko Sakkinen
2025-11-28 16:27     ` James Bottomley

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=aSjP_BsakvhxSDYR@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