From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [PATCH] trace-cmd report: Document --nodate option
Date: Tue, 8 Mar 2022 13:13:54 -0500 [thread overview]
Message-ID: <20220308131354.52452ac1@gandalf.local.home> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
The option --nodate was never documented nor was it even listed in the
trace-cmd report -h usage. Fix that.
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
Documentation/trace-cmd/trace-cmd-report.1.txt | 3 +++
tracecmd/trace-usage.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/Documentation/trace-cmd/trace-cmd-report.1.txt b/Documentation/trace-cmd/trace-cmd-report.1.txt
index 501994a456c8..18e1c5cd0700 100644
--- a/Documentation/trace-cmd/trace-cmd-report.1.txt
+++ b/Documentation/trace-cmd/trace-cmd-report.1.txt
@@ -309,6 +309,9 @@ OPTIONS
Make sure no timestamp goes backwards, and if it does, print out a warning
message of the fact.
+*--nodate*::
+ Ignore converting the timestamps to the date set by *trace-cmd record*(3) --date option.
+
*--raw-ts*::
Display raw timestamps, without any corrections.
diff --git a/tracecmd/trace-usage.c b/tracecmd/trace-usage.c
index ec0af46f0dd2..5e96ca44e9b3 100644
--- a/tracecmd/trace-usage.c
+++ b/tracecmd/trace-usage.c
@@ -244,6 +244,7 @@ static struct usage_help usage_help[] = {
" previous data file, in which case it becomes default\n"
" --ts-diff Show the delta timestamp between events.\n"
" --ts-check Check to make sure no time stamp on any CPU goes backwards.\n"
+ " --nodate Ignore the --date processing of trace-cmd record.\n"
" --raw-ts Display raw timestamps, without any corrections.\n"
" --align-ts Display timestamps aligned to the first event.\n"
" --verbose[=level] Set the desired log level\n"
--
2.34.1
reply other threads:[~2022-03-08 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220308131354.52452ac1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.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).