From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [RFC PATCH] libtraceevent: Add tep_print_selected_fields()
Date: Mon, 2 Aug 2021 12:30:13 -0400 [thread overview]
Message-ID: <20210802123013.460974cb@oasis.local.home> (raw)
In-Reply-To: <0f00d3ec-57a1-8cdf-1ecd-fc6910204f1e@gmail.com>
On Mon, 2 Aug 2021 14:39:11 +0300
Yordan Karadzhov <y.karadz@gmail.com> wrote:
> The implementation of static void tep_print_fmt_field() is incomplete.
> If you compare the logic there with the implementation of
> void tep_print_field() you will see that I am not handling the case of
> a field that is an "ARRAY".
>
> Any ideas what is the best way to handle this case?
I think my reply to your patch should cover this.
-- Steve
next prev parent reply other threads:[~2021-08-02 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 11:27 [RFC PATCH] libtraceevent: Add tep_print_selected_fields() Yordan Karadzhov (VMware)
2021-08-02 11:39 ` Yordan Karadzhov
2021-08-02 16:30 ` Steven Rostedt [this message]
2021-08-02 16:29 ` Steven Rostedt
2021-08-03 12:42 ` Yordan Karadzhov
2021-08-03 13:48 ` 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=20210802123013.460974cb@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).