From: Steven Rostedt <rostedt@goodmis.org>
To: <linux-trace-devel@vger.kernel.org>
Cc: Sameeruddin shaik <sameeross1994@gmail.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: [PATCH 0/4] libtracefs: Updates to tracefs_tracer_set()
Date: Fri, 25 Jun 2021 18:17:35 -0400 [thread overview]
Message-ID: <20210625221739.1215557-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Make tracefs_tracer_set() have an optional argument to allow for custom
tracers, for newer or custom kernels.
Update errno values.
Cleanups and documenation.
This is based on top of Sameer's patch:
https://patchwork.kernel.org/project/linux-trace-devel/patch/1621351602-3703-1-git-send-email-sameeross1994@gmail.com/
Steven Rostedt (VMware) (4):
libtracefs: Add custom tracer to tracefs_tracer_set()
libtracefs: Fix the errno values of tracefs_tracer_set()
libtracefs: Check tracer parameter first in tracefs_tracer_set()
libtracefs: Add documentation for tracefs_tracer_set/clear()
Documentation/libtracefs-tracer.txt | 221 ++++++++++++++++++++++++++++
include/tracefs.h | 3 +-
src/tracefs-tools.c | 46 ++++--
3 files changed, 258 insertions(+), 12 deletions(-)
create mode 100644 Documentation/libtracefs-tracer.txt
--
2.30.2
next reply other threads:[~2021-06-25 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 22:17 Steven Rostedt [this message]
2021-06-25 22:17 ` [PATCH 1/4] libtracefs: Add custom tracer to tracefs_tracer_set() Steven Rostedt
2021-06-25 22:17 ` [PATCH 2/4] libtracefs: Fix the errno values of tracefs_tracer_set() Steven Rostedt
2021-06-25 22:17 ` [PATCH 3/4] libtracefs: Check tracer parameter first in tracefs_tracer_set() Steven Rostedt
2021-06-25 22:17 ` [PATCH 4/4] libtracefs: Add documentation for tracefs_tracer_set/clear() 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=20210625221739.1215557-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sameeross1994@gmail.com \
/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.