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-7.1-rc1
Date: Mon, 20 Apr 2026 00:52:41 +0300 [thread overview]
Message-ID: <aeVOqT605cwcFtnu@kernel.org> (raw)
In-Reply-To: <CAHk-=wiPWCUHsNvzKep7z4VGaL-Brx6Zmh7Efn28WWTPbwn5dA@mail.gmail.com>
On Sun, Apr 19, 2026 at 08:40:36AM -0700, Linus Torvalds wrote:
> On Sun, 19 Apr 2026 at 05:38, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > This pull request contains accumulated bug fixes for TPM driver.
>
> This is all very recent, not all of it has been in linux-next at all,
> and stuff that appears to have been there has been rebased.
>
> Why?
>
> Linus
Responded for both in keys PR but why it came so late has a QA story
behind it.
I created this week a uefi bootable buildroot target (I have tpm in the
gpios) for RPi 400 and tried to get first QA round with it but I run
into some systemd issues.
The upside (and the goal for doing that) is that for future releases I
will bare-metal testing on aarch64 for all commits that pass through.
Should have just given up on that for the time being earlier...
BR, Jarkko
prev parent reply other threads:[~2026-04-19 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 12:38 [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-7.1-rc1 Jarkko Sakkinen
2026-04-19 15:40 ` Linus Torvalds
2026-04-19 21:52 ` 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=aeVOqT605cwcFtnu@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 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.