From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH v2 0/4] Modifications of some 'hist' APIs
Date: Fri, 24 Sep 2021 12:56:58 +0300 [thread overview]
Message-ID: <20210924095702.151826-1-y.karadz@gmail.com> (raw)
The patch-set contains various minor modifications inspired by my first
experience using the 'hist' APIs of libtracefs.
This patch-set applies on top of patches
'libtracefs: Fix code indentation' and
'libtracefs: Fix add_sort_key()'
Yordan Karadzhov (VMware) (4):
libtracefs: Add new constructors for histograms
libtracefs: Transform tracefs_hist_add_sort_key()
libtracefs: Add new 'hist' APIs
libtracefs: Update 'hist' documentation
Documentation/libtracefs-hist-cont.txt | 30 ++++--
Documentation/libtracefs-hist.txt | 80 ++++++++-------
include/tracefs.h | 26 ++++-
src/tracefs-hist.c | 132 +++++++++++++++++++++----
4 files changed, 207 insertions(+), 61 deletions(-)
--
2.30.2
next reply other threads:[~2021-09-24 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 9:56 Yordan Karadzhov (VMware) [this message]
2021-09-24 9:56 ` [PATCH v2 1/4] libtracefs: Add new constructors for histograms Yordan Karadzhov (VMware)
2021-09-24 15:51 ` Tzvetomir Stoyanov
2021-09-24 15:54 ` Steven Rostedt
2021-09-24 16:53 ` Yordan Karadzhov
2021-09-24 9:57 ` [PATCH v2 2/4] libtracefs: Transform tracefs_hist_add_sort_key() Yordan Karadzhov (VMware)
2021-09-24 15:51 ` Tzvetomir Stoyanov
2021-09-24 16:56 ` Yordan Karadzhov
2021-11-10 22:43 ` Steven Rostedt
2021-09-24 9:57 ` [PATCH v2 3/4] libtracefs: Add new 'hist' APIs Yordan Karadzhov (VMware)
2021-09-24 9:57 ` [PATCH v2 4/4] libtracefs: Update 'hist' documentation Yordan Karadzhov (VMware)
2021-10-11 13:55 ` [RFC] Modifications of some 'hist' APIs Yordan Karadzhov
2021-10-13 2:14 ` 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=20210924095702.151826-1-y.karadz@gmail.com \
--to=y.karadz@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).