From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/6] libtracefs: Clean up of the source directory
Date: Tue, 08 Dec 2020 16:54:04 -0500 [thread overview]
Message-ID: <20201208215404.135186972@goodmis.org> (raw)
Steven Rostedt (VMware) (6):
libtracefs: Move features.mk into scripts directory
libtracefs: Remove LIBTRACEFS_DIR as it is the same as bdir
libtracefs: Use LIBTRACEFS_STATIC/SHARED instead of open coding them
libtracefs: Move source files to new src/ directory
libtracefs: Use pkg-config to find libtraceevent
libtracefs: Have make clean remove the .so.X file
----
Makefile | 54 +++++++++++-----------------
features.mk => scripts/features.mk | 0
tracefs-events.c => src/tracefs-events.c | 0
tracefs-instance.c => src/tracefs-instance.c | 0
tracefs-utils.c => src/tracefs-utils.c | 0
utest/Makefile | 2 +-
6 files changed, 22 insertions(+), 34 deletions(-)
rename features.mk => scripts/features.mk (100%)
rename tracefs-events.c => src/tracefs-events.c (100%)
rename tracefs-instance.c => src/tracefs-instance.c (100%)
rename tracefs-utils.c => src/tracefs-utils.c (100%)
next reply other threads:[~2020-12-08 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 21:54 Steven Rostedt [this message]
2020-12-08 21:54 ` [PATCH 1/6] libtracefs: Move features.mk into scripts directory Steven Rostedt
2020-12-08 21:54 ` [PATCH 2/6] libtracefs: Remove LIBTRACEFS_DIR as it is the same as bdir Steven Rostedt
2020-12-08 21:54 ` [PATCH 3/6] libtracefs: Use LIBTRACEFS_STATIC/SHARED instead of open coding them Steven Rostedt
2020-12-08 21:54 ` [PATCH 4/6] libtracefs: Move source files to new src/ directory Steven Rostedt
2020-12-08 21:54 ` [PATCH 5/6] libtracefs: Use pkg-config to find libtraceevent Steven Rostedt
2020-12-08 21:54 ` [PATCH 6/6] libtracefs: Have make clean remove the .so.X file Steven Rostedt
2020-12-09 14:49 ` [PATCH 0/6] libtracefs: Clean up of the source directory Tzvetomir Stoyanov
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=20201208215404.135186972@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.