From: Will Deacon <will@kernel.org>
To: Zenghui Yu <zenghui.yu@linux.dev>
Cc: Jijie Shao <shaojijie@huawei.com>,
jonathan.cameron@huawei.com, mark.rutland@arm.com,
yangyicong@hisilicon.com, chenhao418@huawei.com,
shenjian15@huawei.com, wangjie125@huawei.com,
liuyonglong@huawei.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 drivers/perf: hisi:] drivers/perf: hisi: Update HiSilicon PMU maintainers
Date: Fri, 25 Aug 2023 11:25:22 +0100 [thread overview]
Message-ID: <20230825102522.GA24076@willie-the-truck> (raw)
In-Reply-To: <9009693a-0314-9526-e57f-1b2302abfd7e@linux.dev>
On Fri, Aug 25, 2023 at 12:07:32AM +0800, Zenghui Yu wrote:
> On 2023/8/24 10:41, Jijie Shao wrote:
> > Since Guangbin and Shaokun have left HiSilicon and will no longer
> > maintain the drivers, update the maintainer information and
> > thanks for their work.
> >
> > Signed-off-by: Jijie Shao <shaojijie@huawei.com>
> > Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Acked-by: Yicong Yang <yangyicong@hisilicon.com>
> > ---
> > changeLog
> > v2:
> > 1. update "HISILICON HNS3 PMU DRIVER" to "HISILICON NETWORK SUBSYSTEM 3 PMU DRIVER"
> > suggested by Jonathan
> > 2. update pach subject suggested by Yicong
> > v1: https://lore.kernel.org/all/20230822122812.2384393-1-shaojijie@huawei.com/
> > ---
> > MAINTAINERS | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 4171d3a102a9..df3418780b0c 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -9304,8 +9304,8 @@ F: drivers/crypto/hisilicon/hpre/hpre.h
> > 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>
> > +HISILICON NETWORK SUBSYSTEM 3 PMU DRIVER (HNS3 PMU)
> > +M: Jijie Shao <shaojijie@huawei.com>
> > S: Supported
> > F: Documentation/admin-guide/perf/hns3-pmu.rst
> > F: drivers/perf/hisilicon/hns3_pmu.c
>
> You probably need to move the entry around to keep things ordered
> (see commit 80e62bc8487b).
I'll just leave the title of the entry as it is to avoid the churn.
Will
next prev parent reply other threads:[~2023-08-25 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 2:41 [PATCH V2 drivers/perf: hisi:] drivers/perf: hisi: Update HiSilicon PMU maintainers Jijie Shao
2023-08-24 16:07 ` Zenghui Yu
2023-08-25 10:25 ` Will Deacon [this message]
2023-08-28 1:40 ` Jijie Shao
2023-08-25 12:35 ` 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=20230825102522.GA24076@willie-the-truck \
--to=will@kernel.org \
--cc=chenhao418@huawei.com \
--cc=jonathan.cameron@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=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=zenghui.yu@linux.dev \
/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).