mbox series

[GIT,PULL] TPM DEVICE DRIVER: tpmdd-next-6.11-rc1

Message ID D2EBML829ZJI.1XZZVLVGUXRBH@kernel.org (mailing list archive)
State New
Headers show
Series [GIT,PULL] TPM DEVICE DRIVER: tpmdd-next-6.11-rc1 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-next-6.11-rc1

Message

Jarkko Sakkinen July 1, 2024, 3:51 p.m. UTC
The following changes since commit 22a40d14b572deb80c0648557f4bd502d7e83826:

  Linux 6.10-rc6 (2024-06-30 14:40:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-next-6.11-rc1

for you to fetch changes up to 0543f29408a151c1c4a12e5da07ec45c2779b9b8:

  tpm_tis_spi: add missing attpm20p SPI device ID entry (2024-07-01 15:50:02 +0000)

----------------------------------------------------------------
Hi,

Contains couuple of bug fixes.

BR, Jarkko

----------------------------------------------------------------
Joe Hattori (1):
      char: tpm: Fix possible memory leak in tpm_bios_measurements_open()

Vitor Soares (1):
      tpm_tis_spi: add missing attpm20p SPI device ID entry

 drivers/char/tpm/eventlog/common.c  | 2 ++
 drivers/char/tpm/tpm_tis_spi_main.c | 1 +
 2 files changed, 3 insertions(+)

Comments

Linus Torvalds July 1, 2024, 4:35 p.m. UTC | #1
On Mon, 1 Jul 2024 at 08:51, Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> Contains couple of bug fixes.

This - and your keys pull - say 6.11-rc1 (and say "next"), but don't
really look like the usual merge window stuff.

Just checking.

            Linus
Jarkko Sakkinen July 1, 2024, 5:16 p.m. UTC | #2
On Mon Jul 1, 2024 at 4:35 PM UTC, Linus Torvalds wrote:
> On Mon, 1 Jul 2024 at 08:51, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > Contains couple of bug fixes.
>
> This - and your keys pull - say 6.11-rc1 (and say "next"), but don't
> really look like the usual merge window stuff.

No new features are coming for this release. I had one in progress but
decided to let it mature up until 6.12 [1]. I have one known bug fix
upcoming [2], which I'll send after I've received feedback from Stefan
Berger [3].

The second reason for postponing features is that deploying encrypted
bus is a substantial infrastructural change so it is better to have
bandwidth to fix any possible issues when it ends up to production
kernels.

So yeah, not a usual pull request, but it is still planned unusual one...

>
> Just checking.
>
>             Linus

[1] https://lore.kernel.org/linux-integrity/20240528210823.28798-1-jarkko@kernel.org/T/#t
[2] https://lore.kernel.org/linux-integrity/20240701170735.109583-1-jarkko@kernel.org/T/#u
[3] https://lore.kernel.org/linux-integrity/9f86a167074d9b522311715c567f1c19b88e3ad4.camel@kernel.org/ 

BR, Jarkko