From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Sizhe Liu <liusizhe5@huawei.com>,
Jie Zhan <zhanjie9@hisilicon.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Cc: <linuxarm@huawei.com>, <linux-pci@vger.kernel.org>,
<jic23@kernel.org>, Yicong Yang <yangyccccc@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Update HiSilicon PCI Trace and Tune maintainer
Date: Thu, 16 Apr 2026 11:06:19 +0100 [thread overview]
Message-ID: <20260416110619.0000678a@huawei.com> (raw)
In-Reply-To: <20260416094219.25258-1-Jonathan.Cameron@huawei.com>
On Thu, 16 Apr 2026 10:42:19 +0100
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> Yicong left Huawei a while back so drop both of our entries and add one for
> Sizhe Liu who will be looking after this code going forwards.
+Cc Yicong (Sorry!)
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> MAINTAINERS | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d1cc0e12fe1f..79efa7b94c9e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11572,8 +11572,7 @@ F: drivers/perf/hisilicon
> F: tools/perf/pmu-events/arch/arm64/hisilicon/
>
> HISILICON PTT DRIVER
> -M: Yicong Yang <yangyicong@hisilicon.com>
> -M: Jonathan Cameron <jonathan.cameron@huawei.com>
> +M: Sizhe Liu <liusizhe5@huawei.com>
> L: linux-kernel@vger.kernel.org
> S: Maintained
> F: Documentation/ABI/testing/sysfs-bus-event_source-devices-hisi_ptt
next prev parent reply other threads:[~2026-04-16 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 9:42 [PATCH] MAINTAINERS: Update HiSilicon PCI Trace and Tune maintainer Jonathan Cameron
2026-04-16 10:06 ` Jonathan Cameron [this message]
2026-04-16 17:11 ` Yicong Yang
2026-04-16 11:12 ` Jie Zhan
2026-04-22 2:30 ` Sizhe Liu
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=20260416110619.0000678a@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liusizhe5@huawei.com \
--cc=suzuki.poulose@arm.com \
--cc=yangyccccc@gmail.com \
--cc=zhanjie9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.