From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: John Kacur <jkacur@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] rtla: Documentation: Fix -t, --trace
Date: Thu, 16 May 2024 09:40:40 +0200 [thread overview]
Message-ID: <ff1ec7dc-2164-47bd-9046-4c6ad99947f7@kernel.org> (raw)
In-Reply-To: <20240515183024.59985-2-jkacur@redhat.com>
On 5/15/24 20:30, John Kacur wrote:
> +++ b/Documentation/tools/rtla/common_timerlat_options.rst
^^^^^^
> @@ -22,6 +22,10 @@
> Save the stack trace at the *IRQ* if a *Thread* latency is higher than the
> argument in us.
>
> +**-t**, **--trace** \[*file*]
> +
> + Save the stopped trace to [*file|osnoise_trace.txt*].
> +
The move also allow us to fix this: s/osnoise/timerlat/ ^^^^
It is an error at the man page.
-- Daniel
prev parent reply other threads:[~2024-05-16 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 18:30 [PATCH v3 1/2] rtla: Fix -t\--trace[=file] John Kacur
2024-05-15 18:30 ` [PATCH v3 2/2] rtla: Documentation: Fix -t, --trace John Kacur
2024-05-16 7:40 ` Daniel Bristot de Oliveira [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=ff1ec7dc-2164-47bd-9046-4c6ad99947f7@kernel.org \
--to=bristot@kernel.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--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).