From: "huangguangbin (A)" <huangguangbin2@huawei.com>
To: <john.garry@huawei.com>, <will@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<liuqi115@huawei.com>, <zhangshaokun@hisilicon.com>,
<f.fangjian@huawei.com>, <lipeng321@huawei.com>,
<shenjian15@huawei.com>, <moyufeng@huawei.com>
Subject: Re: [PATCH V3 0/2] drivers/perf: hisi: Add driver for HNS3 PMU
Date: Mon, 11 Apr 2022 09:36:58 +0800 [thread overview]
Message-ID: <bfec5dc5-cb6e-e27e-f233-7f16e53edab7@huawei.com> (raw)
In-Reply-To: <20220329113930.37631-1-huangguangbin2@huawei.com>
Gentle ping. Any comment or suggestion is appreciated. Thanks
On 2022/3/29 19:39, Guangbin Huang wrote:
> Change logs:
> V2 -> V3:
> - Modify the comments of John Garry.
> - Link: https://lore.kernel.org/linux-arm-kernel/20220228123955.30284-1-huangguangbin2@huawei.com/
> V1 -> V2:
> - Modify the comments of John Garry.
> - Link: https://lore.kernel.org/linux-arm-kernel/20220117015222.9617-1-huangguangbin2@huawei.com/
>
> Guangbin Huang (2):
> drivers/perf: hisi: Add description for HNS3 PMU driver
> drivers/perf: hisi: add driver for HNS3 PMU
>
> Documentation/admin-guide/perf/hns3-pmu.rst | 136 ++
> MAINTAINERS | 6 +
> drivers/perf/hisilicon/Kconfig | 10 +
> drivers/perf/hisilicon/Makefile | 1 +
> drivers/perf/hisilicon/hns3_pmu.c | 1640 +++++++++++++++++++
> include/linux/cpuhotplug.h | 1 +
> 6 files changed, 1794 insertions(+)
> create mode 100644 Documentation/admin-guide/perf/hns3-pmu.rst
> create mode 100644 drivers/perf/hisilicon/hns3_pmu.c
>
prev parent reply other threads:[~2022-04-11 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 11:39 [PATCH V3 0/2] drivers/perf: hisi: Add driver for HNS3 PMU Guangbin Huang
2022-03-29 11:39 ` [PATCH V3 1/2] drivers/perf: hisi: Add description for HNS3 PMU driver Guangbin Huang
2022-03-29 11:39 ` [PATCH V3 2/2] drivers/perf: hisi: add driver for HNS3 PMU Guangbin Huang
2022-04-14 11:45 ` John Garry
2022-04-16 10:37 ` huangguangbin (A)
2022-04-25 8:14 ` John Garry
2022-04-11 1:36 ` huangguangbin (A) [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=bfec5dc5-cb6e-e27e-f233-7f16e53edab7@huawei.com \
--to=huangguangbin2@huawei.com \
--cc=f.fangjian@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=liuqi115@huawei.com \
--cc=mark.rutland@arm.com \
--cc=moyufeng@huawei.com \
--cc=shenjian15@huawei.com \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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;
as well as URLs for NNTP newsgroup(s).