From: Will Deacon <will@kernel.org>
To: mark.rutland@arm.com, Junhao He <hejunhao3@huawei.com>,
jonathan.cameron@huawei.com, linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
yangyicong@huawei.com, linux-arm-kernel@lists.infradead.org,
prime.zeng@hisilicon.com, linux-doc@vger.kernel.org,
shenyang39@huawei.com, linuxarm@huawei.com
Subject: Re: [PATCH v5 0/3] Add support for HiSilicon SoC uncore PMU
Date: Fri, 16 Jun 2023 12:59:47 +0100 [thread overview]
Message-ID: <168691485865.2084286.3095107717244593062.b4-ty@kernel.org> (raw)
In-Reply-To: <20230615125926.29832-1-hejunhao3@huawei.com>
On Thu, 15 Jun 2023 20:59:23 +0800, Junhao He wrote:
> Add support for HiSilicon UC/H60PA/PAv3 PMU driver.
>
> PAv3 PMU: Compared with the PAv2 PMU, the PAv3 PMU has different event.
> The PAv3 PMU removed some events which are supported by PAv2 PMU. The
> older PA PMU driver will probe v3 as v2. Add the HISI0275 HID for PAv3
> PMU to distinguish different.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/3] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver
https://git.kernel.org/will/c/1a51688474c0
[2/3] drivers/perf: hisi: Add support for HiSilicon UC PMU driver
https://git.kernel.org/will/c/312eca95e28d
[3/3] docs: perf: Add new description for HiSilicon UC PMU
https://git.kernel.org/will/c/ea8d1c062a0e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-06-16 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:59 [PATCH v5 0/3] Add support for HiSilicon SoC uncore PMU Junhao He
2023-06-15 12:59 ` [PATCH v5 1/3] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver Junhao He
2023-06-16 10:43 ` Mark Rutland
2023-06-15 12:59 ` [PATCH v5 2/3] drivers/perf: hisi: Add support for HiSilicon UC " Junhao He
2023-06-15 12:59 ` [PATCH v5 3/3] docs: perf: Add new description for HiSilicon UC PMU Junhao He
2023-06-16 11:59 ` Will Deacon [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=168691485865.2084286.3095107717244593062.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=hejunhao3@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=shenyang39@huawei.com \
--cc=yangyicong@huawei.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