From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Integrity <linux-integrity@vger.kernel.org>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: tpm: tpm-security: Demote "Null Primary Key Certification in Userspace" section
Date: Tue, 04 Nov 2025 22:32:50 -0500 [thread overview]
Message-ID: <a8a5b95e06e2d5d1c04aab8933f25cd07903a3e8.camel@HansenPartnership.com> (raw)
In-Reply-To: <aQqvEsdoj0El2Dq4@archie.me>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Wed, 2025-11-05 at 08:57 +0700, Bagas Sanjaya wrote:
> On Tue, Nov 04, 2025 at 09:55:08AM -0500, James Bottomley wrote:
> > On Tue, 2025-11-04 at 20:13 +0700, Bagas Sanjaya wrote:
> > > The last section heading in TPM security docs is formatted as
> > > title heading instead. As such, it shows up as TPM toctree entry.
> > > Demote it to section heading as appropriate.
> >
> > It's supposed to be a separate heading. It's explaining how to
> > certify your booted kernel rather than describing TPM security
> > within the kernel.
>
> Should I keep the whole section as-is or should I move it to separate
> docs?
Why might it need moving?
Regards,
James
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2025-11-05 3:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 13:13 [PATCH] Documentation: tpm: tpm-security: Demote "Null Primary Key Certification in Userspace" section Bagas Sanjaya
2025-11-04 14:55 ` James Bottomley
2025-11-05 1:57 ` Bagas Sanjaya
2025-11-05 3:32 ` James Bottomley [this message]
2025-11-05 13:04 ` Bagas Sanjaya
2025-11-05 16:33 ` James Bottomley
2025-11-05 23:23 ` Bagas Sanjaya
2025-11-09 4:50 ` Jarkko Sakkinen
2025-11-09 12:29 ` Bagas Sanjaya
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=a8a5b95e06e2d5d1c04aab8933f25cd07903a3e8.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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