From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: Ross Zwisler <zwisler@google.com>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [PATCH v2 0/3] libtraceeval: Add man pages for traceeval_delta
Date: Fri, 6 Oct 2023 16:12:11 -0400 [thread overview]
Message-ID: <20231006201214.1385447-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Add the necessary man pages for traceeval_delta.
Changes since v1: https://lore.kernel.org/all/20231006185405.1379249-1-rostedt@goodmis.org/
- Updated them to show that traceeval_delta_teval_put() only needs the teval
and not the tdelta.
Steven Rostedt (Google) (3):
libtraceeval: Add man pages for traceeval_delta init/start/stop
functions
libtraceeval: Add man pages for insert/remove/query of traceeval_delta
items
libtraceeval: Add man pages for libtraceeval_delta retrieving of
deltas
Documentation/libtraceeval-delta-init.txt | 346 ++++++++++++++++++++
Documentation/libtraceeval-delta-insert.txt | 122 +++++++
Documentation/libtraceeval-delta-rest.txt | 308 +++++++++++++++++
Documentation/libtraceeval.txt | 65 ++++
check-manpages.sh | 2 +-
5 files changed, 842 insertions(+), 1 deletion(-)
create mode 100644 Documentation/libtraceeval-delta-init.txt
create mode 100644 Documentation/libtraceeval-delta-insert.txt
create mode 100644 Documentation/libtraceeval-delta-rest.txt
--
2.40.1
next reply other threads:[~2023-10-06 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 20:12 Steven Rostedt [this message]
2023-10-06 20:12 ` [PATCH v2 1/3] libtraceeval: Add man pages for traceeval_delta init/start/stop functions Steven Rostedt
2023-10-06 20:12 ` [PATCH v2 2/3] libtraceeval: Add man pages for insert/remove/query of traceeval_delta items Steven Rostedt
2023-10-06 20:12 ` [PATCH v2 3/3] libtraceeval: Add man pages for libtraceeval_delta retrieving of deltas 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=20231006201214.1385447-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=zwisler@google.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 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).