From: Slavomir Kaslev <kaslevs@vmware.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 0/3] trace-cmd: Fix some bugs that include issues with --max-graph-depth
Date: Thu, 13 Jun 2019 14:51:47 +0000 [thread overview]
Message-ID: <CAE0o1NuCo-vhX9j6G_OnYi=UwMETv+eH=881z1oryzJ_6=JKuQ@mail.gmail.com> (raw)
In-Reply-To: <20190612181927.608151291@goodmis.org>
On Wed, Jun 12, 2019 at 9:21 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
>
> Some last minute bugs that were found and fixed.
>
> Steven Rostedt (VMware) (3):
> trace-cmd: Fix typo in Makefile bidr to bdir
> trace-cmd: Have --max-graph-depth only be part of instance
> trace-cmd: Check the return of get_file_content() before calling add_reset_file()
>
> ----
> tracecmd/Makefile | 2 +-
> tracecmd/include/trace-local.h | 2 ++
> tracecmd/trace-record.c | 33 +++++++++++++++++++--------------
> 3 files changed, 22 insertions(+), 15 deletions(-)
Looks good to me.
Reviewed-by: Slavomir Kaslev <kaslevs@vmware.com>
Cheers,
--Slavi
next prev parent reply other threads:[~2019-06-13 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 18:19 [PATCH 0/3] trace-cmd: Fix some bugs that include issues with --max-graph-depth Steven Rostedt
2019-06-12 18:19 ` [PATCH 1/3] trace-cmd: Fix typo in Makefile bidr to bdir Steven Rostedt
2019-06-13 14:40 ` Tzvetomir Stoyanov
2019-06-12 18:19 ` [PATCH 2/3] trace-cmd: Have --max-graph-depth only be part of instance Steven Rostedt
2019-06-13 14:48 ` Tzvetomir Stoyanov
2019-06-12 18:19 ` [PATCH 3/3] trace-cmd: Check the return of get_file_content() before calling add_reset_file() Steven Rostedt
2019-06-13 14:51 ` Tzvetomir Stoyanov
2019-06-13 14:51 ` Slavomir Kaslev [this message]
2019-06-13 14:56 ` [PATCH 0/3] trace-cmd: Fix some bugs that include issues with --max-graph-depth 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='CAE0o1NuCo-vhX9j6G_OnYi=UwMETv+eH=881z1oryzJ_6=JKuQ@mail.gmail.com' \
--to=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=slavomir.kaslev@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).