From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v7 0/4] libtraceevent: Optimize the print of tep fields
Date: Wed, 8 Sep 2021 16:06:57 -0400 [thread overview]
Message-ID: <20210908160657.57db2b5d@oasis.local.home> (raw)
In-Reply-To: <20210823095618.138887-1-y.karadz@gmail.com>
On Mon, 23 Aug 2021 12:56:14 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> Yordan Karadzhov (VMware) (4):
> libtraceevent: Improve tep_print_field()
> libtraceevent: Optimize tep_print_fields()
I accepted the first two patches. I had a comment for the one below.
-- Steve
> libtraceevent: Add APIs for printing the fields of a record
> libtraceevent: Add documentation for the new printing APIs
>
> Documentation/libtraceevent-field_print.txt | 11 +-
> Documentation/libtraceevent.txt | 2 +
> src/event-parse.c | 184 ++++++++++++++++----
> src/event-parse.h | 7 +
> 4 files changed, 170 insertions(+), 34 deletions(-)
>
prev parent reply other threads:[~2021-09-08 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 9:56 [PATCH v7 0/4] libtraceevent: Optimize the print of tep fields Yordan Karadzhov (VMware)
2021-08-23 9:56 ` [PATCH v7 1/4] libtraceevent: Improve tep_print_field() Yordan Karadzhov (VMware)
2021-08-23 9:56 ` [PATCH v7 2/4] libtraceevent: Optimize tep_print_fields() Yordan Karadzhov (VMware)
2021-08-23 9:56 ` [PATCH v7 3/4] libtraceevent: Add APIs for printing the fields of a record Yordan Karadzhov (VMware)
2021-09-08 20:04 ` Steven Rostedt
2021-08-23 9:56 ` [PATCH v7 4/4] libtraceevent: Add documentation for the new printing APIs Yordan Karadzhov (VMware)
2021-09-08 20:06 ` Steven Rostedt [this message]
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=20210908160657.57db2b5d@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=y.karadz@gmail.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).