From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] kernel-shark-qt: Add I/O for configuration data.
Date: Tue, 21 Aug 2018 11:36:39 -0400 [thread overview]
Message-ID: <20180821113639.43293ad2@gandalf.local.home> (raw)
In-Reply-To: <20180817145845.29651-1-y.karadz@gmail.com>
On Fri, 17 Aug 2018 17:58:45 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> Add to the C API of KernelShark instruments for importing/exporting
> configuration settings to/from Json files. A wrapper is added in order
> to abstract out completely the use of Json. This can be useful in the
> future if we want to support multiple formats (YAML for example).
>
> This version of the patch contains a number of improvements suggested
> by Steven Rostedt. Thanks Steven!
>
> Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
>
I pushed the 3 patches upstream.
Thanks Yordan!
-- Steve
prev parent reply other threads:[~2018-08-21 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 14:58 [PATCH v4 2/3] kernel-shark-qt: Add I/O for configuration data Yordan Karadzhov (VMware)
2018-08-21 15:36 ` 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=20180821113639.43293ad2@gandalf.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).