From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Stuart Yoder <stuart.yoder@arm.com>
Cc: 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: Tue, 11 Mar 2025 12:10:25 +0200 [thread overview]
Message-ID: <Z9AMEZw1dm80mwx0@kernel.org> (raw)
In-Reply-To: <20250311210011.18b7ab80@canb.auug.org.au>
On Tue, Mar 11, 2025 at 09:00:11PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tpmdd tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/security/tpm/tpm_ffa_crb.rst: WARNING: document isn't included in any toctree
>
> Introduced by commit
>
> 115be78c0bfe ("Documentation: tpm: add documentation for the CRB FF-A interface")
>
> --
> Cheers,
> Stephen Rothwell
Stuart, could you send a replacement patch and I'll repeal and replace?
BR, Jarkko
next prev parent reply other threads:[~2025-03-11 10:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 10:00 linux-next: build warning after merge of the tpmdd tree Stephen Rothwell
2025-03-11 10:10 ` Jarkko Sakkinen [this message]
2025-03-11 14:21 ` Stuart Yoder
2025-03-12 6:16 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 6:21 Stephen Rothwell
2024-05-06 10:48 ` Bagas Sanjaya
2024-05-06 10:55 ` Bagas Sanjaya
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=Z9AMEZw1dm80mwx0@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stuart.yoder@arm.com \
/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 NNTP newsgroup(s).