From: Namhyung Kim <namhyung@kernel.org>
To: "Thomas Falcon" <thomas.falcon@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Caleb Biggers" <caleb.biggers@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Ian Rogers" <irogers@google.com>
Subject: Re: [PATCH v2 00/15] perf vendor events: Update Intel events
Date: Tue, 08 Jul 2025 10:15:24 -0700 [thread overview]
Message-ID: <175199492491.1307843.10305341895448801662.b4-ty@kernel.org> (raw)
In-Reply-To: <20250630163101.1920170-1-irogers@google.com>
On Mon, 30 Jun 2025 09:30:45 -0700, Ian Rogers wrote:
> Update:
> - ADL/ADLN v1.29 -> 1.31
> - ARL 1.08 -> 1.09
> - CLX 1.23 -> 1.25
> - EMR 1.11 -> 1.14
> - GRR 1.07 -> 1.09
> - GNR 1.08 -> 1.10
> - ICX 1.27 -> 1.28
> - LNL 1.11 -> 1.14
> - MTL 1.13 -> 1.14
> - PTL new v1.00
> - SPR 1.25 -> 1.28
> - SRF 1.09 -> 1.11
> - SKX 1.36 -> 1.37
> - TGL 1.17 -> 1.18
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-07-08 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 16:30 Ian Rogers
2025-06-30 16:30 ` [PATCH v2 01/15] perf vendor events: Update Alderlake events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 02/15] perf vendor events: Update AlderlakeN events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 03/15] perf vendor events: Update Arrowlake events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 04/15] perf vendor events: Update CascadelakeX events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 05/15] perf vendor events: Update EmeraldRapids events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 06/15] perf vendor events: Update GrandRidge events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 07/15] perf vendor events: Update GraniteRapids events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 08/15] perf vendor events: Update IcelakeX events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 09/15] perf vendor events: Update LunarLake events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 10/15] perf vendor events: Update MeteorLake events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 11/15] perf vendor events: Add PantherLake events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 12/15] perf vendor events: Update SapphireRapids events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 13/15] perf vendor events: Update SierraForest events Ian Rogers
2025-06-30 16:30 ` [PATCH v2 14/15] perf vendor events: Update SkylakeX events Ian Rogers
2025-06-30 16:31 ` [PATCH v2 15/15] perf vendor events: Update TigerLake events Ian Rogers
2025-07-07 21:50 ` [PATCH v2 00/15] perf vendor events: Update Intel events Falcon, Thomas
2025-07-08 17:15 ` Namhyung Kim [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=175199492491.1307843.10305341895448801662.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.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
all inboxes | Powered by JetHome®