Linux-Next Archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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: linux-next: build warning after merge of the tpmdd tree
Date: Mon, 6 May 2024 16:21:05 +1000	[thread overview]
Message-ID: <20240506162105.42ce2ff7@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

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")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-05-06  6:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  6:21 Stephen Rothwell [this message]
2024-05-06 10:48 ` linux-next: build warning after merge of the tpmdd tree Bagas Sanjaya
2024-05-06 10:55   ` Bagas Sanjaya
  -- 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=20240506162105.42ce2ff7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).