From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 14:11:37 -0400 [thread overview]
Message-ID: <20240927141137.75ecdf71@gandalf.local.home> (raw)
In-Reply-To: <87a5fte6mj.fsf@trenco.lwn.net>
On Fri, 27 Sep 2024 04:24:52 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> > 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.
Like this?
-- Steve
diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
index 0b300901fd75..f3d235c8438b 100644
--- a/Documentation/trace/index.rst
+++ b/Documentation/trace/index.rst
@@ -5,6 +5,7 @@ Linux Tracing Technologies
.. toctree::
:maxdepth: 2
+ debugging
ftrace-design
tracepoint-analysis
ftrace
next prev parent reply other threads:[~2024-09-27 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240919150513.067dd727@canb.auug.org.au>
2024-09-26 13:14 ` linux-next: build warning after merge of the ftrace tree Steven Rostedt
2024-09-27 10:24 ` Jonathan Corbet
2024-09-27 18:11 ` Steven Rostedt [this message]
2024-09-28 1:15 ` Bagas Sanjaya
[not found] <20201116173502.392a769c@canb.auug.org.au>
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
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=20240927141137.75ecdf71@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=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=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 NNTP newsgroup(s).