From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/5] trace-cmd: Triaging bugzillas and fixes
Date: Wed, 08 Jul 2020 16:28:50 -0400 [thread overview]
Message-ID: <20200708202850.764168067@goodmis.org> (raw)
This includes the two updates Tzvetomir did, as well as fixes for
bugzillas: 207069, 205953, and 204703
Steven Rostedt (VMware) (3):
trace-cmd: Explicitly state what trace-cmd report -f does
tools lib traceevent: Let function symbols be used in operations
trace-cmd: Print raw hex for flags when trace-cmd report -R
Tzvetomir Stoyanov (VMware) (2):
trace-cmd: Fix trace-cmd report -t to show full timestamp
tools lib traceveent: Fix kbuffer_start_of_data() to return the first record
----
Documentation/trace-cmd-report.1.txt | 4 ++-
lib/traceevent/event-parse.c | 49 +++++++++++++++++++++++++++-
lib/traceevent/kbuffer-parse.c | 7 +++-
tracecmd/trace-read.c | 63 ++++++++++++++++++++++++++----------
tracecmd/trace-usage.c | 2 +-
5 files changed, 104 insertions(+), 21 deletions(-)
next reply other threads:[~2020-07-08 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 20:28 Steven Rostedt [this message]
2020-07-08 20:28 ` [PATCH 1/5] trace-cmd: Fix trace-cmd report -t to show full timestamp Steven Rostedt
2020-07-08 20:28 ` [PATCH 2/5] tools lib traceveent: Fix kbuffer_start_of_data() to return the first record Steven Rostedt
2020-07-08 20:28 ` [PATCH 3/5] trace-cmd: Explicitly state what trace-cmd report -f does Steven Rostedt
2020-07-08 20:28 ` [PATCH 4/5] tools lib traceevent: Let function symbols be used in operations Steven Rostedt
2020-07-08 20:28 ` [PATCH 5/5] trace-cmd: Print raw hex for flags when trace-cmd report -R 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=20200708202850.764168067@goodmis.org \
--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).