From: Jiri Olsa <jolsa@redhat.com>
To: Sanskriti Sharma <sansharm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Joe Lawrence <joe.lawrence@redhat.com>
Subject: Re: [PATCH 0/5] perf tool: small coverity clean ups
Date: Tue, 2 Oct 2018 18:02:13 +0200 [thread overview]
Message-ID: <20181002160213.GA16200@krava> (raw)
In-Reply-To: <1538490554-8161-1-git-send-email-sansharm@redhat.com>
On Tue, Oct 02, 2018 at 10:29:09AM -0400, Sanskriti Sharma wrote:
> This patch set fixes a few coverity static code analyzer complaints. Build
> tested only.
>
> Sanskriti Sharma (5):
> perf strbuf: match va_{add,copy} with va_end
> perf tools: cleanup trace-event-info 'tdata' leak
> perf tools: free 'printk' string in parse_ftrace_printk()
> perf tools: avoid double free in read_event_file()
> perf tools: free temporary 'sys' string in read_event_files()
nice, thanks for posting those
Reviewed-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> tools/perf/util/strbuf.c | 10 ++++++++--
> tools/perf/util/trace-event-info.c | 2 ++
> tools/perf/util/trace-event-parse.c | 1 +
> tools/perf/util/trace-event-read.c | 9 +++++----
> 4 files changed, 16 insertions(+), 6 deletions(-)
>
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2018-10-02 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 14:29 [PATCH 0/5] perf tool: small coverity clean ups Sanskriti Sharma
2018-10-02 14:29 ` [PATCH 1/5] perf strbuf: match va_{add,copy} with va_end Sanskriti Sharma
2018-10-02 15:45 ` Arnaldo Carvalho de Melo
2018-10-09 5:29 ` [tip:perf/core] perf strbuf: Match " tip-bot for Sanskriti Sharma
2018-10-02 14:29 ` [PATCH 2/5] perf tools: cleanup trace-event-info 'tdata' leak Sanskriti Sharma
2018-10-02 15:47 ` Arnaldo Carvalho de Melo
2018-10-09 5:29 ` [tip:perf/core] perf tools: Cleanup " tip-bot for Sanskriti Sharma
2018-10-02 14:29 ` [PATCH 3/5] perf tools: free 'printk' string in parse_ftrace_printk() Sanskriti Sharma
2018-10-02 15:47 ` Arnaldo Carvalho de Melo
2018-10-09 5:30 ` [tip:perf/core] perf tools: Free " tip-bot for Sanskriti Sharma
2018-10-02 14:29 ` [PATCH 4/5] perf tools: avoid double free in read_event_file() Sanskriti Sharma
2018-10-02 15:48 ` Arnaldo Carvalho de Melo
2018-10-09 5:31 ` [tip:perf/core] perf tools: Avoid " tip-bot for Sanskriti Sharma
2018-10-02 14:29 ` [PATCH 5/5] perf tools: free temporary 'sys' string in read_event_files() Sanskriti Sharma
2018-10-02 15:50 ` Arnaldo Carvalho de Melo
2018-10-09 5:31 ` [tip:perf/core] perf tools: Free " tip-bot for Sanskriti Sharma
2018-10-02 16:02 ` Jiri Olsa [this message]
2018-10-02 16:14 ` [PATCH 0/5] perf tool: small coverity clean ups Arnaldo Carvalho de Melo
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=20181002160213.GA16200@krava \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sansharm@redhat.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).