From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Chun-Tse Shao <ctshao@google.com>
Cc: linux-kernel@vger.kernel.org, Ian Rogers <irogers@google.com>,
peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, adrian.hunter@intel.com,
kan.liang@linux.intel.com, howardchu95@gmail.com,
yeoreum.yun@arm.com, linux@treblig.org, james.clark@linaro.org,
ak@linux.intel.com, weilin.wang@intel.com,
asmadeus@codewreck.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 1/3] perf evlist: Make uniquifying counter names consistent
Date: Mon, 12 May 2025 14:52:24 -0300 [thread overview]
Message-ID: <aCI1WKq1ZmUUpMzt@x1> (raw)
In-Reply-To: <aCI1JRjBBINe0set@x1>
On Mon, May 12, 2025 at 02:51:37PM -0300, Arnaldo Carvalho de Melo wrote:
> Can you please refresh this series?
I mean to what is in:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
branch tmp.perf-tools-next
- Arnaldo
next prev parent reply other threads:[~2025-05-12 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:48 [PATCH v2 0/3] Fix incorrect counts when count the same uncore event multiple times Chun-Tse Shao
2025-03-27 22:48 ` [PATCH v2 1/3] perf evlist: Make uniquifying counter names consistent Chun-Tse Shao
2025-05-12 17:51 ` Arnaldo Carvalho de Melo
2025-05-12 17:52 ` Arnaldo Carvalho de Melo [this message]
2025-03-27 22:48 ` [PATCH v2 2/3] perf parse-events: Use wildcard processing to set an event to merge into Chun-Tse Shao
2025-03-27 22:48 ` [PATCH v2 3/3] perf test: Add stat uniquifying test Chun-Tse Shao
2025-04-03 19:25 ` Ian Rogers
2025-04-23 22:48 ` Chun-Tse Shao
2025-03-28 4:20 ` [PATCH v2 0/3] Fix incorrect counts when count the same uncore event multiple times Ian Rogers
2025-04-29 16:58 ` Chun-Tse Shao
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=aCI1WKq1ZmUUpMzt@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=ctshao@google.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=weilin.wang@intel.com \
--cc=yeoreum.yun@arm.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).