From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] trace-cmd: Fixes for reading older trace-cmd trace.dat files
Date: Fri, 25 Oct 2019 02:52:43 -0400 [thread overview]
Message-ID: <20191025065243.627023108@goodmis.org> (raw)
Fix two bugs that caused reading an trace.dat file created
by an older trace-cmd not to print properly.
Steven Rostedt (VMware) (2):
libtraceevent: Remove extra '\n' in print_event_time()
trace-cmd: Use usecs unless specified not to
----
lib/trace-cmd/trace-input.c | 12 ++++++++----
lib/traceevent/event-parse.c | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
next reply other threads:[~2019-10-25 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 6:52 Steven Rostedt [this message]
2019-10-25 6:52 ` [PATCH 1/2] libtraceevent: Remove extra \n in print_event_time() Steven Rostedt
2019-10-25 6:52 ` [PATCH 2/2] trace-cmd: Use usecs unless specified not to 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=20191025065243.627023108@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.