public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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
Date: Fri, 28 Nov 2025 11:27:47 -0500	[thread overview]
Message-ID: <de28d9eea3a2b7df238afc1815b5934208418910.camel@HansenPartnership.com> (raw)
In-Reply-To: <aSm6CP6avMrqPbAO@kernel.org>

On Fri, 2025-11-28 at 17:04 +0200, Jarkko Sakkinen wrote:
> On Thu, Nov 27, 2025 at 11:18:27PM -0500, James Bottomley wrote:
> > On Fri, 2025-11-28 at 00:26 +0200, Jarkko Sakkinen wrote:
[...]
> > > ----------------------------------------------------------------
> > > Bagas Sanjaya (1):
> > >       Documentation: tpm-security.rst: change title to section
> > > heading
> > 
> > This shouldn't to be in there.  I think you might have missed the
> > discussion where I explained it was supposed to be a separate
> > section:
> > 
> > https://lore.kernel.org/all/50acd6bfbc8b9006bef5d7d0376b7ce4ab35f94c.camel@HansenPartnership.com/
>  
> I can iterate this pull request and drop that out, and while at it,
> add Roberto's reviewed-by tag to the bug fix to the bug fix that caps
> the number of PCR banks.

That would be great, thanks.

Regards,

James


      reply	other threads:[~2025-11-28 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 22:26 [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.19-rc1 Jarkko Sakkinen
2025-11-28  4:18 ` James Bottomley
2025-11-28 15:04   ` Jarkko Sakkinen
2025-11-28 16:27     ` James Bottomley [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=de28d9eea3a2b7df238afc1815b5934208418910.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --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