From: Jijie Shao <shaojijie@huawei.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: <shaojijie@huawei.com>, <will@kernel.org>, <mark.rutland@arm.com>,
<yangyicong@huawei.com>, <chenhao418@huawei.com>,
<shenjian15@huawei.com>, <wangjie125@huawei.com>,
<liuyonglong@huawei.com>, <hejunhao3@huawei.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH drivers/perf: hisi:] drivers/perf: hisi: Update email addresses of HISILICON_PMU driver maintainers.
Date: Thu, 24 Aug 2023 10:00:02 +0800 [thread overview]
Message-ID: <daeec014-c642-c4c0-5b28-eac4eca3aa3d@huawei.com> (raw)
In-Reply-To: <20230823090811.00001f7f@Huawei.com>
on 2023/8/23 16:08, Jonathan Cameron wrote:
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Best wishes and thanks to them both and thanks to yangyicong and
> shaojijie for stepping up.
>
>
> Bit late now, but with hindsight it might have been better
> to use the same wording for the HNS3 PMU as for HNS itself
>
> HISILICON NETWORK SUBSYSTEM 3 PMU Driver (HNS3 PMU)
> so that it would appear in the obviously place in MAINTAINERS
> rather than a few lines further up. Probably not worth
> the noise of changing it however.
>
> Jonathan
>
Hi,
Yeah, I agree. and I think it's worth changing, and I'll change it in V2.
Jijie Shao
>> ---
>> MAINTAINERS | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 4171d3a102a9..a3109267a411 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -9305,7 +9305,7 @@ F: drivers/crypto/hisilicon/hpre/hpre_crypto.c
>> F: drivers/crypto/hisilicon/hpre/hpre_main.c
>>
>> HISILICON HNS3 PMU DRIVER
>> -M: Guangbin Huang <huangguangbin2@huawei.com>
>> +M: Jijie Shao <shaojijie@huawei.com>
>> S: Supported
>> F: Documentation/admin-guide/perf/hns3-pmu.rst
>> F: drivers/perf/hisilicon/hns3_pmu.c
>> @@ -9343,7 +9343,7 @@ F: Documentation/devicetree/bindings/net/hisilicon*.txt
>> F: drivers/net/ethernet/hisilicon/
>>
>> HISILICON PMU DRIVER
>> -M: Shaokun Zhang <zhangshaokun@hisilicon.com>
>> +M: Yicong Yang <yangyicong@hisilicon.com>
>> M: Jonathan Cameron <jonathan.cameron@huawei.com>
>> S: Supported
>> W: http://www.hisilicon.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-24 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:28 [PATCH drivers/perf: hisi:] drivers/perf: hisi: Update email addresses of HISILICON_PMU driver maintainers Jijie Shao
2023-08-23 8:08 ` Jonathan Cameron
2023-08-24 2:00 ` Jijie Shao [this message]
2023-08-23 9:38 ` Yicong Yang
2023-08-24 1:45 ` Jijie Shao
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=daeec014-c642-c4c0-5b28-eac4eca3aa3d@huawei.com \
--to=shaojijie@huawei.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=chenhao418@huawei.com \
--cc=hejunhao3@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=mark.rutland@arm.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.com \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).