From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/4] trace-cmd documentation update for v7 files
Date: Mon, 13 Sep 2021 15:53:18 +0300 [thread overview]
Message-ID: <20210913125322.3682097-1-tz.stoyanov@gmail.com> (raw)
Added documentation of trace file version 7.
This patch-set depends on "[PATCH 00/10] trace-cmd dump - v7 update",
should be applied on top of it:
https://lore.kernel.org/linux-trace-devel/20210913125039.3680986-1-tz.stoyanov@gmail.com/
Tzvetomir Stoyanov (VMware) (4):
trace-cmd: Update bash completion
tarce-cmd: Man page for "trace-cmd convert"
tarce-cmd: Update record man page
trace-cmd: Document trace file version 7
.../trace-cmd/trace-cmd-convert.1.txt | 65 +++
.../trace-cmd/trace-cmd-record.1.txt | 13 +
Documentation/trace-cmd/trace-cmd.1.txt | 4 +-
...e-cmd.dat.5.txt => trace-cmd.dat.v6.5.txt} | 9 +-
.../trace-cmd/trace-cmd.dat.v7.5.txt | 442 ++++++++++++++++++
tracecmd/trace-cmd.bash | 37 ++
6 files changed, 564 insertions(+), 6 deletions(-)
create mode 100644 Documentation/trace-cmd/trace-cmd-convert.1.txt
rename Documentation/trace-cmd/{trace-cmd.dat.5.txt => trace-cmd.dat.v6.5.txt} (98%)
create mode 100644 Documentation/trace-cmd/trace-cmd.dat.v7.5.txt
--
2.31.1
next reply other threads:[~2021-09-13 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:53 Tzvetomir Stoyanov (VMware) [this message]
2021-09-13 12:53 ` [PATCH 1/4] trace-cmd: Update bash completion Tzvetomir Stoyanov (VMware)
2021-09-13 12:53 ` [PATCH 2/4] tarce-cmd: Man page for "trace-cmd convert" Tzvetomir Stoyanov (VMware)
2021-09-13 12:53 ` [PATCH 3/4] tarce-cmd: Update record man page Tzvetomir Stoyanov (VMware)
2021-09-13 12:53 ` [PATCH 4/4] trace-cmd: Document trace file version 7 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=20210913125322.3682097-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).