From: Steven Rostedt <rostedt@goodmis.org>
To: Oscar Shiang <oscar0225@livemail.tw>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Remove duplicated words in trace/osnoise-tracer
Date: Sun, 20 Feb 2022 12:08:14 -0500 [thread overview]
Message-ID: <20220220120814.4f593555@gandalf.local.home> (raw)
In-Reply-To: <TYCP286MB1913117487F390E3BCE38B15A1399@TYCP286MB1913.JPNP286.PROD.OUTLOOK.COM>
On Sun, 20 Feb 2022 20:12:00 +0800
Oscar Shiang <oscar0225@livemail.tw> wrote:
> There are 2 duplicated words found in osnoise tracer documentation.
> This patch removes them.
>
> Signed-off-by: Oscar Shiang <oscar0225@livemail.tw>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> ---
> Documentation/trace/osnoise-tracer.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/osnoise-tracer.rst b/Documentation/trace/osnoise-tracer.rst
> index b648cb9bf..963def9f9 100644
> --- a/Documentation/trace/osnoise-tracer.rst
> +++ b/Documentation/trace/osnoise-tracer.rst
> @@ -51,7 +51,7 @@ For example::
> [root@f32 ~]# cd /sys/kernel/tracing/
> [root@f32 tracing]# echo osnoise > current_tracer
>
> -It is possible to follow the trace by reading the trace trace file::
> +It is possible to follow the trace by reading the trace file::
>
> [root@f32 tracing]# cat trace
> # tracer: osnoise
> @@ -108,7 +108,7 @@ The tracer has a set of options inside the osnoise directory, they are:
> option.
> - tracing_threshold: the minimum delta between two time() reads to be
> considered as noise, in us. When set to 0, the default value will
> - will be used, which is currently 5 us.
> + be used, which is currently 5 us.
>
> Additional Tracing
> ------------------
next prev parent reply other threads:[~2022-02-20 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 12:12 [PATCH] docs: Remove duplicated words in trace/osnoise-tracer Oscar Shiang
2022-02-20 17:08 ` Steven Rostedt [this message]
2022-02-20 20:43 ` Daniel Bristot de Oliveira
2022-02-24 3:34 ` Steven Rostedt
2022-02-24 17:43 ` Jonathan Corbet
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=20220220120814.4f593555@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar0225@livemail.tw \
/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