From: Donglin Peng <pengdonglin@sangfor.com.cn>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
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 ftrace tree
Date: Fri, 23 Jun 2023 14:53:25 +0800 [thread overview]
Message-ID: <b4c091e4-945b-3930-9314-5a04ce828e56@sangfor.com.cn> (raw)
In-Reply-To: <20230623143517.19ffc6c0@canb.auug.org.au>
On 2023/6/23 12:35, Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/trace/ftrace.rst:2797: WARNING: Literal block expected; none found.
> Documentation/trace/ftrace.rst:2816: WARNING: Literal block expected; none found.
>
> Introduced by commit
>
> 21c094d3f8a6 ("tracing: Add documentation for funcgraph-retval and funcgraph-retval-hex")
>
I am so sorry, and I will fix it right now.
next prev parent reply other threads:[~2023-06-23 6:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 4:35 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2023-06-23 6:53 ` Donglin Peng [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=b4c091e4-945b-3930-9314-5a04ce828e56@sangfor.com.cn \
--to=pengdonglin@sangfor.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.