From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the ftrace tree
Date: Fri, 27 Sep 2024 04:24:52 -0600 [thread overview]
Message-ID: <87a5fte6mj.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240926091452.4be87000@rorschach.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Thu, 19 Sep 2024 15:05:13 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> Hi all,
>>
>> After merging the ftrace tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> Documentation/trace/debugging.rst: WARNING: document isn't included in any toctree
>>
>> Introduced by commit
>>
>> 2fcd5aff92aa ("tracing/Documentation: Start a document on how to debug with tracing")
>>
>
> Thanks for reporting this Stephen, but I don't know how to fix it.
>
> Jon?
Add a line to Documentation/trace/index.rst in the appropriate spot
referencing the new file.
jon
next prev parent reply other threads:[~2024-09-27 10:25 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 5:05 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2024-09-24 22:34 ` Stephen Rothwell
2024-09-26 13:14 ` Steven Rostedt
2024-09-27 10:24 ` Jonathan Corbet [this message]
2024-09-27 18:11 ` Steven Rostedt
2024-09-28 1:15 ` Bagas Sanjaya
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 8:38 Stephen Rothwell
2025-03-27 7:01 Stephen Rothwell
2025-03-27 8:07 ` Gabriele Monaco
2024-05-15 2:48 Stephen Rothwell
2024-05-15 4:49 ` Steven Rostedt
2024-05-15 5:01 ` Steven Rostedt
2024-05-15 5:11 ` Stephen Rothwell
2024-05-15 5:13 ` Stephen Rothwell
2023-06-23 4:35 Stephen Rothwell
2023-06-23 6:53 ` Donglin Peng
2022-11-25 3:10 Stephen Rothwell
2021-10-28 12:23 Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 21:10 ` Stephen Rothwell
2021-10-28 21:29 ` Kalesh Singh
2021-10-28 22:36 ` Stephen Rothwell
2021-10-28 21:30 ` Steven Rostedt
2021-10-25 23:35 Stephen Rothwell
2021-10-26 12:15 ` Masami Hiramatsu
2021-10-25 4:39 Stephen Rothwell
2021-10-25 6:13 ` Masami Hiramatsu
2021-08-23 9:58 Stephen Rothwell
2021-08-23 14:00 ` Steven Rostedt
2021-08-24 10:53 ` Stephen Rothwell
2020-11-16 6:35 Stephen Rothwell
2020-11-16 17:43 ` Steven Rostedt
2020-11-16 19:24 ` Jonathan Corbet
2020-11-16 20:25 ` Steven Rostedt
2020-11-16 20:29 ` Jonathan Corbet
2020-11-16 20:35 ` Steven Rostedt
2020-08-05 4:21 Stephen Rothwell
2019-11-15 3:02 Stephen Rothwell
2019-11-15 3:43 ` Steven Rostedt
2014-06-04 6:09 Stephen Rothwell
2014-06-04 16:26 ` Steven Rostedt
2014-06-04 16:49 ` Stephen Rothwell
2014-06-05 0:20 ` Fengguang Wu
2014-06-05 1:00 ` Steven Rostedt
2014-06-05 1:03 ` Fengguang Wu
2014-06-05 1:12 ` Steven Rostedt
2014-06-05 1:20 ` Steven Rostedt
2014-06-05 1:33 ` Fengguang Wu
2014-06-05 1:39 ` Steven Rostedt
2014-06-05 2:14 ` Fengguang Wu
2014-06-05 2:36 ` Steven Rostedt
2014-06-05 2:50 ` Fengguang Wu
2014-06-05 3:03 ` Fengguang Wu
2014-06-05 3:13 ` Steven Rostedt
2014-06-05 3:42 ` Fengguang Wu
2014-06-05 2:38 ` Steven Rostedt
2014-06-05 2:44 ` Fengguang Wu
2014-06-05 2:46 ` Steven Rostedt
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=87a5fte6mj.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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