From: Namhyung Kim <namhyung@kernel.org>
To: Chun-Tse Shao <ctshao@google.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.com, james.clark@linaro.org,
afaerber@suse.de, mani@kernel.org, dapeng1.mi@linux.intel.com,
thomas.falcon@intel.com, irogers@google.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/12] perf vendor events intel: update
Date: Wed, 15 Jul 2026 11:21:44 -0700 [thread overview]
Message-ID: <alfPuIxX95FTv5Jt@google.com> (raw)
In-Reply-To: <CAJpZYjUa4HpbUvPhcjG3-ezKkig8bd1mbdQmb7xo_c9S_uyvfg@mail.gmail.com>
Hi CT,
On Wed, Jul 15, 2026 at 10:35:35AM -0700, Chun-Tse Shao wrote:
> (Please disregard my previous message due to a formatting error, I
> apologize for the spam)
>
> Following feedback from Ian
> (https://lore.kernel.org/all/CAP-5=fVc6tw3hfnvB7n_UZ3B5JF7vBpm7cnE8516t5HVUWwFNQ@mail.gmail.com/),
> we have decided to address this by fixing get_cpuid_str rather than
> modifying mapfile.csv. I will send a separate patch for that.
>
> Please disregard this v2 series and use the v1 series instead:
> https://lore.kernel.org/all/20260713181757.481164-1-ctshao@google.com/
Thanks for the clarification, I will apply v1 then.
Namhyung
prev parent reply other threads:[~2026-07-15 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 20:40 [PATCH v2 0/12] perf vendor events intel: update Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 01/12] perf vendor events intel: Update alderlake events from 1.39 to 1.40 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 02/12] perf vendor events intel: Update alderlaken " Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 03/12] perf vendor events intel: Update arrowlake events from 1.19 to 1.20 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 04/12] perf vendor events intel: Update clearwaterforest events from 1.02 to 1.04 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 05/12] perf vendor events intel: Update grandridge events from 1.12 to 1.13 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 06/12] perf vendor events intel: Update graniterapids events from 1.19 to 1.20 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 07/12] perf vendor events intel: Update lunarlake events from 1.25 to 1.26 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 08/12] perf vendor events intel: Update meteorlake events from 1.21 to 1.22 Chun-Tse Shao
2026-07-14 20:56 ` sashiko-bot
2026-07-14 20:40 ` [PATCH v2 09/12] perf vendor events intel: Add novalake v1.00 events Chun-Tse Shao
2026-07-14 23:29 ` Ian Rogers
2026-07-15 21:18 ` Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 10/12] perf vendor events intel: Update pantherlake events from 1.06 to 1.07 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 11/12] perf vendor events intel: Update sierraforest events from 1.17 to 1.18 Chun-Tse Shao
2026-07-14 20:40 ` [PATCH v2 12/12] perf vendor events intel: Update emeraldrapids metrics Chun-Tse Shao
2026-07-15 17:35 ` [PATCH v2 0/12] perf vendor events intel: update Chun-Tse Shao
2026-07-15 18:21 ` 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=alfPuIxX95FTv5Jt@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.