From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Yuan Can <yuancan@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
Subject: Re: [PATCH 0/5] perf: Remove unused struct
Date: Tue, 27 Sep 2022 13:36:03 +0100 [thread overview]
Message-ID: <YzLuMxMccZ1vn9sm@kernel.org> (raw)
In-Reply-To: <20220927013931.110475-1-yuancan@huawei.com>
Em Tue, Sep 27, 2022 at 01:39:26AM +0000, Yuan Can escreveu:
> This series contains five cleanup patches, remove unused struct.
Thanks, applied.
- Arnaldo
> Yuan Can (5):
> perf machine: Remove unused struct process_args
> perf annotate: Remove unused struct disasm_line_samples
> perf metric: Remove unused struct metric_ref_node
> perf jit: Remove unused struct debug_line_info
> perf lock: Remove unused struct lock_contention_key
>
> tools/perf/ui/browsers/annotate.c | 5 -----
> tools/perf/util/bpf_lock_contention.c | 5 -----
> tools/perf/util/jitdump.c | 7 -------
> tools/perf/util/machine.c | 4 ----
> tools/perf/util/metricgroup.c | 11 -----------
> 5 files changed, 32 deletions(-)
>
> --
> 2.17.1
--
- Arnaldo
prev parent reply other threads:[~2022-09-27 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 1:39 [PATCH 0/5] perf: Remove unused struct Yuan Can
2022-09-27 1:39 ` [PATCH 1/5] perf machine: Remove unused struct process_args Yuan Can
2022-09-27 12:24 ` Arnaldo Carvalho de Melo
2022-09-27 1:39 ` [PATCH 2/5] perf annotate: Remove unused struct disasm_line_samples Yuan Can
2022-09-27 1:39 ` [PATCH 3/5] perf metric: Remove unused struct metric_ref_node Yuan Can
2022-09-27 1:39 ` [PATCH 4/5] perf jit: Remove unused struct debug_line_info Yuan Can
2022-09-27 1:39 ` [PATCH 5/5] perf lock: Remove unused struct lock_contention_key Yuan Can
2022-09-27 12:36 ` 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=YzLuMxMccZ1vn9sm@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@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=yuancan@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).