From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Bagas Sanjaya" <bagasdotme@gmail.com>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH] Documentation: tpm: Add TPM security docs toctree entry
Date: Tue, 07 May 2024 23:07:13 +0300 [thread overview]
Message-ID: <D13OM6OQ0QRS.SSJJRFNR92LJ@kernel.org> (raw)
In-Reply-To: <20240506105936.37073-1-bagasdotme@gmail.com>
On Mon May 6, 2024 at 1:59 PM EEST, Bagas Sanjaya wrote:
> Stephen Rothwell reports htmldocs warning when merging tpmdd tree for
> linux-next:
>
> Documentation/security/tpm/tpm-security.rst: WARNING: document isn't included in any toctree
>
> Add toctree entry for TPM security docs to fix above warning.
>
> Fixes: ddfb3687c538 ("Documentation: add tpm-security.rst")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/linux-next/20240506162105.42ce2ff7@canb.auug.org.au/
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/security/tpm/index.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/security/tpm/index.rst b/Documentation/security/tpm/index.rst
> index f27a17f60a9602..fa593d960040a9 100644
> --- a/Documentation/security/tpm/index.rst
> +++ b/Documentation/security/tpm/index.rst
> @@ -5,6 +5,7 @@ Trusted Platform Module documentation
> .. toctree::
>
> tpm_event_log
> + tpm-security
> tpm_tis
> tpm_vtpm_proxy
> xen-tpmfront
>
> base-commit: 152585665f0f6b89e67ed6d04c17b18d1f0f4077
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
I'll apply asap
BR, Jarkko
prev parent reply other threads:[~2024-05-07 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:59 [PATCH] Documentation: tpm: Add TPM security docs toctree entry Bagas Sanjaya
2024-05-07 20:07 ` 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=D13OM6OQ0QRS.SSJJRFNR92LJ@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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