From: Daniel Bristot de Oliveira <[email protected]>
To: Bagas Sanjaya <[email protected]>,
[email protected], [email protected]
Cc: Steven Rostedt <[email protected]>,
Masami Hiramatsu <[email protected]>,
Jonathan Corbet <[email protected]>,
[email protected],
Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
kernel test robot <[email protected]>
Subject: Re: [PATCH] Documentation/osnoise: escape underscore of NO_ prefix
Date: Fri, 25 Nov 2022 19:16:56 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/25/22 04:43, Bagas Sanjaya wrote:
> kernel test robot reported unknown target name warning:
>
> Documentation/trace/osnoise-tracer.rst:112: WARNING: Unknown target name: "no".
>
> The warning causes NO_ prefix to be rendered as link text instead, which
> points to non-existent link target.
>
> Escape the prefix underscore to fix the warning.
>
> Link: https://lore.kernel.org/linux-doc/[email protected]/
> Fixes: 67543cd6b8eee5 ("Documentation/osnoise: Add osnoise/options documentation")
> Reported-by: kernel test robot <[email protected]>
> Signed-off-by: Bagas Sanjaya <[email protected]>
Acked-by: Daniel Bristot de Oliveira <[email protected]>
Thanks!
-- Daniel
next prev parent reply other threads:[~2022-11-25 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 20:49 [ammarfaizi2-block:rostedt/linux-trace/ftrace/core 10/12] htmldocs: Documentation/trace/osnoise-tracer.rst:112: WARNING: Unknown target name: "no" kernel test robot
2022-11-25 3:43 ` [PATCH] Documentation/osnoise: escape underscore of NO_ prefix Bagas Sanjaya
2022-11-25 18:16 ` Daniel Bristot de Oliveira [this message]
2022-11-28 20:50 ` Steven Rostedt
2022-12-03 10:35 ` Jonathan Corbet
2022-12-03 13:54 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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