From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Integrity <linux-integrity@vger.kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, 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: Sun, 9 Nov 2025 19:29:00 +0700 [thread overview]
Message-ID: <e5e3a542-ee07-4fe5-a6d5-2bc5b2fa873f@gmail.com> (raw)
In-Reply-To: <aRAdiUB9otJk5i9U@kernel.org>
On 11/9/25 11:50, Jarkko Sakkinen wrote:
> On Tue, Nov 04, 2025 at 08:13:12PM +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.
>>
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>> ---
>> Documentation/security/tpm/tpm-security.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/security/tpm/tpm-security.rst b/Documentation/security/tpm/tpm-security.rst
>> index 4f633f2510336b..bf73bbe66db2fa 100644
>> --- a/Documentation/security/tpm/tpm-security.rst
>> +++ b/Documentation/security/tpm/tpm-security.rst
>> @@ -153,7 +153,7 @@ protect key sealing and parameter decryption to protect key unsealing
>> and random number generation.
>>
>> Null Primary Key Certification in Userspace
>> -===========================================
>> +-------------------------------------------
>>
>> Every TPM comes shipped with a couple of X.509 certificates for the
>> primary endorsement key. This document assumes that the Elliptic
>>
>> base-commit: 27600b51fbc8b9a4eba18c8d88d7edb146605f3f
>> --
>> An old man doll... just what I always wanted! - Clara
>>
>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> Should I pick this?
>
Of course!
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2025-11-09 12:29 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
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 [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=e5e3a542-ee07-4fe5-a6d5-2bc5b2fa873f@gmail.com \
--to=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