From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] trace-cmd: A couple of fixes
Date: Thu, 19 Dec 2019 16:48:05 -0500 [thread overview]
Message-ID: <20191219214805.821145530@goodmis.org> (raw)
Here's a couple of fixes to bugs that I found while playing with
the p2p code.
Steven Rostedt (VMware) (2):
trace-cmd: Duplicate trace_clock in tracecmd_input handle
tools lib traceevent: Add builtin handler for trace_marker_raw
----
lib/trace-cmd/trace-input.c | 7 ++++++
lib/traceevent/plugins/plugin_function.c | 41 ++++++++++++++++++++++++++++++++
2 files changed, 48 insertions(+)
next reply other threads:[~2019-12-19 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 21:48 Steven Rostedt [this message]
2019-12-19 21:48 ` [PATCH 1/2] trace-cmd: Duplicate trace_clock in tracecmd_input handle Steven Rostedt
2019-12-19 21:48 ` [PATCH 2/2] tools lib traceevent: Add builtin handler for trace_marker_raw 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=20191219214805.821145530@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).