From: Kalesh Singh <kaleshsingh@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: surenb@google.com, hridya@google.com, kernel-team@android.com,
rostedt@goodmis.org, sfr@canb.auug.org.au,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Kalesh Singh <kaleshsingh@google.com>
Subject: [PATCH] tracing/histogram: Fix documentation inline emphasis warning
Date: Thu, 28 Oct 2021 10:05:48 -0700 [thread overview]
Message-ID: <20211028170548.2597449-1-kaleshsingh@google.com> (raw)
In-Reply-To: <20211028091646.15f6e6de@gandalf.local.home>
This fixes the warning:
Documentation/trace/histogram.rst:1766: WARNING: Inline emphasis
start-string without end-string
The issue was caused by an unescaped '*' character.
Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
Documentation/trace/histogram.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histogram.rst
index e12699abaee8..66ec972dfb78 100644
--- a/Documentation/trace/histogram.rst
+++ b/Documentation/trace/histogram.rst
@@ -1764,7 +1764,7 @@ using the same key and variable from yet another event::
# echo 'hist:key=pid:wakeupswitch_lat=$wakeup_lat+$switchtime_lat ...' >> event3/trigger
Expressions support the use of addition, subtraction, multiplication and
-division operators (+-*/).
+division operators (+-\*/).
Note that division by zero always returns -1.
--
2.33.0.1079.g6e70778dc9-goog
next prev parent reply other threads:[~2021-10-28 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:23 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 17:05 ` Kalesh Singh [this message]
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
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=20211028170548.2597449-1-kaleshsingh@google.com \
--to=kaleshsingh@google.com \
--cc=hridya@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
/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).