From: Jonathan Corbet <corbet@lwn.net>
To: Pierre Gondois <pierre.gondois@arm.com>, linux-kernel@vger.kernel.org
Cc: Pierre Gondois <pierre.gondois@arm.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-devel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: rtla: Correct command line example
Date: Thu, 13 Oct 2022 10:37:37 -0600 [thread overview]
Message-ID: <87tu47isry.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221006084409.3882542-1-pierre.gondois@arm.com>
Pierre Gondois <pierre.gondois@arm.com> writes:
> The '-t/-T' parameters seem to have been swapped:
> -t/--trace[=file]: save the stopped trace
> to [file|timerlat_trace.txt]
> -T/--thread us: stop trace if the thread latency
> is higher than the argument in us
>
> Swap them back.
>
> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
> ---
> Documentation/tools/rtla/rtla-timerlat-top.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/tools/rtla/rtla-timerlat-top.rst b/Documentation/tools/rtla/rtla-timerlat-top.rst
> index 1c321de1c171..7c4e4b109493 100644
> --- a/Documentation/tools/rtla/rtla-timerlat-top.rst
> +++ b/Documentation/tools/rtla/rtla-timerlat-top.rst
> @@ -39,7 +39,7 @@ higher than *30 us*. It is also set to stop the session if a *Thread* timer
> latency higher than *30 us* is hit. Finally, it is set to save the trace
> buffer if the stop condition is hit::
>
> - [root@alien ~]# rtla timerlat top -s 30 -t 30 -T
> + [root@alien ~]# rtla timerlat top -s 30 -T 30 -t
> Timer Latency
Applied, thanks.
jon
prev parent reply other threads:[~2022-10-13 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 8:44 [PATCH] Documentation: rtla: Correct command line example Pierre Gondois
2022-10-12 12:51 ` Daniel Bristot de Oliveira
2022-10-13 16:37 ` Jonathan Corbet [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=87tu47isry.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bristot@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=rostedt@goodmis.org \
/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).