From: Namhyung Kim <namhyung@kernel.org>
To: john.g.garry@oracle.com, will@kernel.org, james.clark@linaro.org,
leo.yan@linux.dev, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
Mike Leach <mike.leach@arm.com>,
Besar Wicaksono <bwicaksono@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tmakin@nvidia.com, vsethi@nvidia.com, rwiley@nvidia.com,
skelley@nvidia.com, rajjoshi@nvidia.com, treding@nvidia.com,
jonathanh@nvidia.com, mochs@nvidia.com, sauravsc@amazon.com
Subject: Re: [PATCH 0/2] perf vendor events arm64: Fix Tegra410 Olympus PMU events
Date: Wed, 19 Aug 2026 10:08:30 -0700 [thread overview]
Message-ID: <178715931078.2811574.8141825092501896684.b4-ty@kernel.org> (raw)
In-Reply-To: <20260813170155.1156593-1-bwicaksono@nvidia.com>
On Thu, 13 Aug 2026 17:01:53 +0000, Besar Wicaksono wrote:
> Fix two issues in the NVIDIA Tegra410 Olympus PMU event definitions:
>
> - Correct the swapped MetricGroup assignments for the L1 data and
> instruction prefetcher metrics.
> - Correct the name and description of implementation-defined event
> 0x0197.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2026-08-19 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:01 Besar Wicaksono
2026-08-13 17:01 ` [PATCH 1/2] perf vendor events arm64: fix swapped MetricGroup for Tegra410 L1 prefetcher metrics Besar Wicaksono
2026-08-13 17:01 ` [PATCH 2/2] perf vendor events arm64: Fix Tegra410 Olympus event 0x0197 Besar Wicaksono
2026-08-17 4:13 ` [PATCH 0/2] perf vendor events arm64: Fix Tegra410 Olympus PMU events Ian Rogers
2026-08-19 17:08 ` 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=178715931078.2811574.8141825092501896684.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bwicaksono@nvidia.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@arm.com \
--cc=mingo@redhat.com \
--cc=mochs@nvidia.com \
--cc=peterz@infradead.org \
--cc=rajjoshi@nvidia.com \
--cc=rwiley@nvidia.com \
--cc=sauravsc@amazon.com \
--cc=skelley@nvidia.com \
--cc=tmakin@nvidia.com \
--cc=treding@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=will@kernel.org \
/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®