From: Leo Yan <leo.yan@linux.dev>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Besar Wicaksono <bwicaksono@nvidia.com>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"john.g.garry@oracle.com" <john.g.garry@oracle.com>,
"james.clark@arm.com" <james.clark@arm.com>,
"mike.leach@linaro.org" <mike.leach@linaro.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"irogers@google.com" <irogers@google.com>,
"alisaidi@amazon.com" <alisaidi@amazon.com>,
Vikram Sethi <vsethi@nvidia.com>, Rich Wiley <rwiley@nvidia.com>,
Yifei Wan <YWan@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>,
Sean Kelley <skelley@nvidia.com>
Subject: Re: [PATCH v1 0/3] arm64: Support Neoverse-V2 for Perf Arm SPE
Date: Wed, 1 May 2024 04:26:55 +0800 [thread overview]
Message-ID: <20240430202655.GF125@debian-dev> (raw)
In-Reply-To: <SJ0PR12MB56767ECAF499949C4689E91BA01A2@SJ0PR12MB5676.namprd12.prod.outlook.com>
On Tue, Apr 30, 2024 at 05:50:40PM +0000, Besar Wicaksono wrote:
> Hi Arnaldo,
>
> Could you take these changes for perf?
> [2/3] tools headers arm64: Add Neoverse-V2 part
> [3/3] perf arm-spe: Add Neoverse-V2 to neoverse list
Thanks for bringing up this.
I confirmed this patch series can be cleanly applied on the mainline
kernel, so the above two patches look good to me.
Thanks,
Leo
next prev parent reply other threads:[~2024-04-30 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 19:23 [PATCH v1 0/3] arm64: Support Neoverse-V2 for Perf Arm SPE Besar Wicaksono
2024-01-09 19:23 ` [PATCH v1 1/3] arm64: Add Neoverse-V2 part Besar Wicaksono
2024-01-09 19:23 ` [PATCH v1 2/3] tools headers " Besar Wicaksono
2024-01-09 19:23 ` [PATCH v1 3/3] perf arm-spe: Add Neoverse-V2 to neoverse list Besar Wicaksono
2024-01-10 1:14 ` Leo Yan
2024-01-10 9:12 ` [PATCH v1 0/3] arm64: Support Neoverse-V2 for Perf Arm SPE James Clark
2024-04-15 15:56 ` Besar Wicaksono
2024-04-30 17:50 ` Besar Wicaksono
2024-04-30 20:26 ` Leo Yan [this message]
2024-04-19 15:32 ` Will Deacon
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=20240430202655.GF125@debian-dev \
--to=leo.yan@linux.dev \
--cc=YWan@nvidia.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=jonathanh@nvidia.com \
--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@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rwiley@nvidia.com \
--cc=skelley@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).