From: Bagas Sanjaya <bagasdotme@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.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: Thu, 6 Nov 2025 06:23:46 +0700 [thread overview]
Message-ID: <aQvcgoOU0AHxKf9W@archie.me> (raw)
In-Reply-To: <bbba0752a40859a114bac987d279a8b268e5e5eb.camel@HansenPartnership.com>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Wed, Nov 05, 2025 at 11:33:39AM -0500, James Bottomley wrote:
> On Wed, 2025-11-05 at 20:04 +0700, Bagas Sanjaya wrote:
> > > Why might it need moving?
> >
> > Just to tidy up toctree then...
>
> I'd really rather have the files in the doc tree grouped for ease (and
> reminder of) maintenance. The two headings belong together in one file
> because if someone updates the doc for one, there's at least a chance
> they'll notice the other might need an update as well; whereas if we do
> separate files for every heading the tree becomes very fragmented and
> the chance of something being missed increases.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-05 23:23 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 [this message]
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=aQvcgoOU0AHxKf9W@archie.me \
--to=bagasdotme@gmail.com \
--cc=James.Bottomley@hansenpartnership.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