From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the tpmdd tree
Date: Mon, 6 May 2024 17:55:44 +0700 [thread overview]
Message-ID: <65817e22-6cc8-4433-ad35-e3c556f390a8@gmail.com> (raw)
In-Reply-To: <Zji1jB9xqOo3es5g@archie.me>
On 5/6/24 17:48, Bagas Sanjaya wrote:
> On Mon, May 06, 2024 at 04:21:05PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the tpmdd tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> Documentation/security/tpm/tpm-security.rst: WARNING: document isn't included in any toctree
>>
>> Introduced by commit
>>
>> ddfb3687c538 ("Documentation: add tpm-security.rst")
>>
>
> Duh! I should have added the toctree for that doc when reviewing it. I will be
> sending the fixup shortly.
>
Oops, I feel like had not reviewed that doc.
Sorry for inconvenience.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2024-05-06 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 6:21 linux-next: build warning after merge of the tpmdd tree Stephen Rothwell
2024-05-06 10:48 ` Bagas Sanjaya
2024-05-06 10:55 ` Bagas Sanjaya [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-11 4:52 Stephen Rothwell
2019-06-13 15:13 ` Jarkko Sakkinen
2019-02-07 2:47 Stephen Rothwell
2019-02-07 21:16 ` Jarkko Sakkinen
2018-01-02 2:50 Stephen Rothwell
2018-01-02 4:05 ` Shaikh, Azhar
2017-09-07 2:31 Stephen Rothwell
2017-09-07 8:43 ` Colin Ian King
2017-09-07 16:21 ` Jarkko Sakkinen
2016-11-15 1:01 Stephen Rothwell
2016-11-15 2:13 ` Jarkko Sakkinen
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=65817e22-6cc8-4433-ad35-e3c556f390a8@gmail.com \
--to=bagasdotme@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jarkko@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).