From: Steven Rostedt <rostedt@goodmis.org>
To: Donglin Peng <pengdonglin@sangfor.com.cn>
Cc: mhiramat@kernel.org, sfr@canb.auug.org.au,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] tracing: fix warnings when building htmldocs
Date: Fri, 23 Jun 2023 10:46:56 -0400 [thread overview]
Message-ID: <20230623104656.7039aa05@gandalf.local.home> (raw)
In-Reply-To: <20230623071728.25688-1-pengdonglin@sangfor.com.cn>
Remember to also Cc linux-trace-kernel@vger.kernel.org
(I pulled it in regardless)
And I also updated the subject to be:
tracing: Fix warnings when building htmldocs for function graph retval
As it should start with a capital letter, and be more specific than just
general htmldoc fix.
-- Steve
On Fri, 23 Jun 2023 15:17:28 +0800
Donglin Peng <pengdonglin@sangfor.com.cn> wrote:
> When building htmldocs, the following warnings appear:
>
> Documentation/trace/ftrace.rst:2797: WARNING: Literal block expected; none found.
> Documentation/trace/ftrace.rst:2816: WARNING: Literal block expected; none found.
>
> So fix it.
>
> Signed-off-by: Donglin Peng <pengdonglin@sangfor.com.cn>
> ---
> Documentation/trace/ftrace.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index df2d3e57a83f..172f35c7308f 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -2786,7 +2786,7 @@ option, and these limitations will be eliminated in the future:
> especially when larger types are truncated, whether explicitly or implicitly.
> Here are some specific cases to illustrate this point:
>
> - **Case One**::
> + **Case One**:
>
> The function narrow_to_u8 is defined as follows::
>
> @@ -2805,7 +2805,7 @@ option, and these limitations will be eliminated in the future:
> If you pass 0x123456789abcdef to this function and want to narrow it,
> it may be recorded as 0x123456789abcdef instead of 0xef.
>
> - **Case Two**::
> + **Case Two**:
>
> The function error_if_not_4g_aligned is defined as follows::
>
prev parent reply other threads:[~2023-06-23 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 7:17 [PATCH] tracing: fix warnings when building htmldocs Donglin Peng
2023-06-23 8:37 ` Masami Hiramatsu
2023-06-23 14:46 ` Steven Rostedt [this message]
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=20230623104656.7039aa05@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=pengdonglin@sangfor.com.cn \
--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