public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Yushan Wang <wangyushan12@huawei.com>, <conor@kernel.org>
Cc: <arnd@arndb.de>, <catalin.marinas@arm.com>, <will@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <linuxarm@huawei.com>,
	<liuyonglong@huawei.com>, <prime.zeng@hisilicon.com>,
	<fanghao11@huawei.com>, <wangzhou1@hisilicon.com>
Subject: Re: [PATCH] MAINTAINERS: Add myself as maintainer of hisi_soc_hha
Date: Thu, 8 Jan 2026 16:22:57 +0000	[thread overview]
Message-ID: <20260108162257.00000a2b@huawei.com> (raw)
In-Reply-To: <20260108133128.777813-1-wangyushan12@huawei.com>

On Thu, 8 Jan 2026 21:31:28 +0800
Yushan Wang <wangyushan12@huawei.com> wrote:

> Add myself as maintainer of HiSilicon SoC HHA driver as I will be
> responsible for this driver.
> 
> Signed-off-by: Yushan Wang <wangyushan12@huawei.com>
Acked-by: Jonathan Cameron <jonathan.cameron@huawei.com>

Thanks for stepping up!

Jonathan
> 
> ---
>  MAINTAINERS | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a0dd762f5648..b8427c072c9e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11366,6 +11366,11 @@ F:	Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
>  F:	drivers/soc/hisilicon/kunpeng_hccs.c
>  F:	drivers/soc/hisilicon/kunpeng_hccs.h
>  
> +HISILICON SOC HHA DRIVER
> +M:	Yushan Wang <wangyushan12@huawei.com>
> +S:	Maintained
> +F:	drivers/cache/hisi_soc_hha.c
> +
>  HISILICON LPC BUS DRIVER
>  M:	Jay Fang <f.fangjian@huawei.com>
>  S:	Maintained


  reply	other threads:[~2026-01-08 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 13:31 [PATCH] MAINTAINERS: Add myself as maintainer of hisi_soc_hha Yushan Wang
2026-01-08 16:22 ` Jonathan Cameron [this message]
2026-01-09 21:31 ` Conor Dooley
  -- strict thread matches above, loose matches on Subject: below --
2026-01-28 19:56 Conor Dooley

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=20260108162257.00000a2b@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=fanghao11@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=wangyushan12@huawei.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=will@kernel.org \
    /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