From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Shang XiaoJing <shangxiaojing@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] perf: Clean up and fix potential mem leak
Date: Tue, 6 Sep 2022 09:43:08 -0300 [thread overview]
Message-ID: <YxdAXFowH/JbPV78@kernel.org> (raw)
In-Reply-To: <20220906032906.21395-1-shangxiaojing@huawei.com>
Em Tue, Sep 06, 2022 at 11:29:03AM +0800, Shang XiaoJing escreveu:
> Some clean up in perf.c and builtin-c2c.c.
>
> changes from v2:
> - clear omissible free label in c2c_he_zalloc.
Thanks, applied [12]/3 to perf/core for Linux v6.1.
- Arnaldo
> Shang XiaoJing (3):
> perf clean: Add same_cmd_with_prefix helper
> perf c2c: Add helpers to get counts of loads or stores
> perf c2c: Prevent potential memory leak in c2c_he_zalloc
>
> tools/perf/builtin-c2c.c | 77 +++++++++++++++++++---------------------
> tools/perf/perf.c | 12 +++++--
> 2 files changed, 46 insertions(+), 43 deletions(-)
>
> --
> 2.17.1
--
- Arnaldo
prev parent reply other threads:[~2022-09-06 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 3:29 [PATCH v2 0/3] perf: Clean up and fix potential mem leak Shang XiaoJing
2022-09-06 3:29 ` [PATCH v2 1/3] perf clean: Add same_cmd_with_prefix helper Shang XiaoJing
2022-09-06 3:29 ` [PATCH v2 2/3] perf c2c: Add helpers to get counts of loads or stores Shang XiaoJing
2022-09-06 4:28 ` Leo Yan
2022-09-06 3:29 ` [PATCH v2 3/3] perf c2c: Prevent potential memory leak in c2c_he_zalloc Shang XiaoJing
2022-09-06 4:31 ` Leo Yan
2022-09-06 12:40 ` Arnaldo Carvalho de Melo
2022-09-06 12:43 ` Arnaldo Carvalho de Melo [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=YxdAXFowH/JbPV78@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=shangxiaojing@huawei.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).