From: Tzvetomir Stoyanov <tstoyanov@vmware.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/3] Few patches, related to libtracevent APIs
Date: Tue, 19 Mar 2019 13:19:21 +0200 [thread overview]
Message-ID: <20190319111924.17443-1-tstoyanov@vmware.com> (raw)
This patchset introduces new libtracevent APIs, which can be used for
accessing struct tep_handler fields. It also changes the description
of few APIs, to match more closely their logic.
There are also fixes to coding style problems, introduced by previous patches.
Tzvetomir Stoyanov (3):
tools/lib/traceevent: Change description of few APIs
tools/lib/traceevent: Coding style fixes
tools/lib/traceevent: Implement new traceevent APIs for accessing
struct tep_handler fields
tools/lib/traceevent/event-parse-api.c | 190 +++++++++++++++++++----
tools/lib/traceevent/event-parse-local.h | 2 +
tools/lib/traceevent/event-parse.c | 4 +-
tools/lib/traceevent/event-parse.h | 12 +-
tools/lib/traceevent/plugin_kvm.c | 2 +-
5 files changed, 173 insertions(+), 37 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-19 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 11:19 Tzvetomir Stoyanov [this message]
2019-03-19 11:19 ` [PATCH 1/3] tools/lib/traceevent: Change description of few APIs Tzvetomir Stoyanov
2019-03-20 15:48 ` Matt Helsley
2019-03-19 11:19 ` [PATCH 2/3] tools/lib/traceevent: Coding style fixes Tzvetomir Stoyanov
2019-03-20 15:53 ` Matt Helsley
2019-03-19 11:19 ` [PATCH 3/3] tools/lib/traceevent: Implement new traceevent APIs for accessing struct tep_handler fields Tzvetomir Stoyanov
2019-03-20 16:32 ` Matt Helsley
2019-03-21 9:26 ` Tzvetomir Stoyanov
2019-03-21 10:03 ` Tzvetomir Stoyanov
2019-03-21 12:59 ` Steven Rostedt
2019-03-21 19:24 ` Steven Rostedt
2019-03-21 19:46 ` Steven Rostedt
2019-03-22 11:33 ` Tzvetomir Stoyanov
2019-03-22 12:16 ` Steven Rostedt
2019-03-22 12:49 ` Tzvetomir Stoyanov
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=20190319111924.17443-1-tstoyanov@vmware.com \
--to=tstoyanov@vmware.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).