From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/3] trace-cmd: Various updates and fixes
Date: Fri, 24 Jan 2020 21:50:08 -0500 [thread overview]
Message-ID: <20200125025008.757057369@goodmis.org> (raw)
Steven Rostedt (VMware) (3):
tracefs: Include -ltracecmd to libtracefs.so build
trace-cmd: Remove error processing from write_file() use error_log instead
trace-cmd: Fix the looping to clear triggers and filters
----
lib/tracefs/Makefile | 2 +
tracecmd/trace-record.c | 310 +++++++++++++++++++++++++++++++++---------------
2 files changed, 219 insertions(+), 93 deletions(-)
next reply other threads:[~2020-01-25 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 2:50 Steven Rostedt [this message]
2020-01-25 2:50 ` [PATCH 1/3] tracefs: Include -ltracecmd to libtracefs.so build Steven Rostedt
2020-01-25 2:50 ` [PATCH 2/3] trace-cmd: Remove error processing from write_file() use error_log instead Steven Rostedt
2020-01-25 2:50 ` [PATCH 3/3] trace-cmd: Fix the looping to clear triggers and filters 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=20200125025008.757057369@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).