From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/5] trace-cmd: A few updates
Date: Wed, 22 Jan 2020 12:12:50 -0500 [thread overview]
Message-ID: <20200122171250.252248737@goodmis.org> (raw)
Some clean ups, and a fix to get the python module working again.
Steven Rostedt (VMware) (5):
trace-cmd: Create TRACECMD_MAGIC macro for magic number of trace-cmd data file
trace-cmd: Place "trace.dat" into the macro DEFAULT_INPUT_FILE
trace-cmd: Add installation of ld.conf.d file for library paths
trace-cmd: Have libtracecmd.so include libtraceevent
trace-cmd: Remove unused trace_util function declarations
----
Makefile | 6 +++++-
include/trace-cmd/trace-cmd.h | 13 ++-----------
lib/trace-cmd/Makefile | 2 ++
lib/trace-cmd/trace-input.c | 2 +-
scripts/utils.mk | 12 +++++++++++-
tracecmd/include/trace-local.h | 1 +
tracecmd/trace-dump.c | 6 ++----
tracecmd/trace-hist.c | 2 +-
tracecmd/trace-mem.c | 2 +-
tracecmd/trace-read.c | 2 +-
tracecmd/trace-record.c | 2 +-
tracecmd/trace-restore.c | 2 +-
tracecmd/trace-split.c | 2 +-
13 files changed, 30 insertions(+), 24 deletions(-)
next reply other threads:[~2020-01-22 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 17:12 Steven Rostedt [this message]
2020-01-22 17:12 ` [PATCH 1/5] trace-cmd: Create TRACECMD_MAGIC macro for magic number of trace-cmd data file Steven Rostedt
2020-01-22 17:12 ` [PATCH 2/5] trace-cmd: Place "trace.dat" into the macro DEFAULT_INPUT_FILE Steven Rostedt
2020-01-22 17:12 ` [PATCH 3/5] trace-cmd: Add installation of ld.conf.d file for library paths Steven Rostedt
2020-01-22 17:22 ` Steven Rostedt
2020-01-22 17:12 ` [PATCH 4/5] trace-cmd: Have libtracecmd.so include libtraceevent Steven Rostedt
2020-01-22 17:12 ` [PATCH 5/5] trace-cmd: Remove unused trace_util function declarations 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=20200122171250.252248737@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.