From: Markus Elfring <Markus.Elfring@web.de>
To: Chen Wandun <chenwandun@huawei.com>,
Cheng Jian <cj.chengjian@huawei.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3 0/2] Fixing memory leaks in perf events parser
Date: Mon, 15 Jun 2020 10:30:18 +0200 [thread overview]
Message-ID: <1ee927e5-2bb6-a72c-8705-95bc6cacf719@web.de> (raw)
In-Reply-To: <20200615013614.8646-1-chenwandun@huawei.com>
> fix some memleaks in parse_events_term__sym_hw and parse_events_term__clone.
Can it be more appropriate to refer to the term “memory leak” in consistent ways?
> v1 ==> v2
> 1. split into two patches
Corresponding development consequences can become more interesting.
> v2 ==> v3
> add more commit log.
>
> Chen Wandun (1):
> perf tools: fix potential memleak in perf events parser
>
> Cheng Jian (1):
> perf tools: fix potential memleak in perf events parser
>
> tools/perf/util/parse-events.c | 51 ++++++++++++++++++++++++++++------
Are there any chances to make the change distinction a bit easier
by adjusting such commit subjects?
Regards,
Markus
next parent reply other threads:[~2020-06-15 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200615013614.8646-1-chenwandun@huawei.com>
2020-06-15 8:30 ` Markus Elfring [this message]
[not found] ` <20200615013614.8646-2-chenwandun@huawei.com>
2020-06-15 8:45 ` [PATCH v3 1/2] perf tools: Fix potential memory leaks in perf events parser Markus Elfring
[not found] ` <20200615013614.8646-3-chenwandun@huawei.com>
2020-06-15 8:54 ` [PATCH v3 2/2] " Markus Elfring
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=1ee927e5-2bb6-a72c-8705-95bc6cacf719@web.de \
--to=markus.elfring@web.de \
--cc=acme@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenwandun@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
/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).