From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: [PATCH 0/3] trace-cmd: Clean up library and KernelShark remnants
Date: Mon, 26 Jul 2021 12:28:54 -0400 [thread overview]
Message-ID: <20210726162857.487153-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Remove leftover remnants of building KernelShark, libtraceevent and
libtracefs from the trace-cmd Makefiles.
Steven Rostedt (VMware) (3):
trace-cmd: Remove traceevent/ and tracefs/ from include headers
trace-cmd: Remove leftover traces of libtraceevent in Makefiles
trace-cmd: Remove remnants of KernelShark build
.gitignore | 1 -
Makefile | 39 ++-----------------
include/trace-cmd/trace-cmd.h | 4 +-
.../include/private/trace-cmd-private.h | 2 +-
lib/trace-cmd/trace-util.c | 4 +-
python/Makefile | 2 +-
6 files changed, 9 insertions(+), 43 deletions(-)
--
2.30.2
next reply other threads:[~2021-07-26 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:28 Steven Rostedt [this message]
2021-07-26 16:28 ` [PATCH 1/3] trace-cmd: Remove traceevent/ and tracefs/ from include headers Steven Rostedt
2021-07-26 16:28 ` [PATCH 2/3] trace-cmd: Remove leftover traces of libtraceevent in Makefiles Steven Rostedt
2021-07-26 16:28 ` [PATCH 3/3] trace-cmd: Remove remnants of KernelShark build 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=20210726162857.487153-1-rostedt@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).