From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v3 0/2] libtracefs man pages
Date: Tue, 22 Dec 2020 06:53:02 +0200 [thread overview]
Message-ID: <20201222045304.369175-1-tz.stoyanov@gmail.com> (raw)
Initial implementation of libtracefs man pages.
v3 changes:
- Removed accpeted patches from the set.
- Fixed description of the tracing_dir parameter, to be the same
in all man pages.
- Removed "<event-parse.h>" includes.
v2 changes:
- Removed tracefs_find_tracing_dir() API
- Renamed tracefs_get_tracing_dir() to tracefs_tracing_dir()
- Removed any references to "#include <event-parse.h>"
- Rewrote some descriptions, as suggested by Steven.
Tzvetomir Stoyanov (VMware) (2):
libtracefs man pages: APIs for initializing a tep handler with trace
events from the local system.
libtracefs man pages: helper APIs for working with trace file system.
Documentation/libtracefs-events-tep.txt | 130 ++++++++++++++++++++++++
Documentation/libtracefs-utils.txt | 103 +++++++++++++++++++
2 files changed, 233 insertions(+)
create mode 100644 Documentation/libtracefs-events-tep.txt
create mode 100644 Documentation/libtracefs-utils.txt
--
2.28.0
next reply other threads:[~2020-12-22 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 4:53 Tzvetomir Stoyanov (VMware) [this message]
2020-12-22 4:53 ` [PATCH v3 1/2] libtracefs man pages: APIs for initializing a tep handler with trace events from the local system Tzvetomir Stoyanov (VMware)
2020-12-22 4:53 ` [PATCH v3 2/2] libtracefs man pages: helper APIs for working with trace file system Tzvetomir Stoyanov (VMware)
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=20201222045304.369175-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).