[PATCH] MAINTAINERS: Update HiSilicon SPI Controller driver maintainer

[PATCH] MAINTAINERS: Update HiSilicon SPI Controller driver maintainer

[Yang Shen]

Add Yang Shen as the maintainer of the HiSilicon SPI Controller driver,
replacing Jay Fang.

Signed-off-by: Yang Shen <shenyang39@huawei.com>
Reviewed-by: Jay Fang <f.fangjian@huawei.com>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 7d2074d16107..73e3af200eec 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10883,7 +10883,7 @@ F:	drivers/crypto/hisilicon/sec2/sec_crypto.h
 F:	drivers/crypto/hisilicon/sec2/sec_main.c
 
 HISILICON SPI Controller DRIVER FOR KUNPENG SOCS
-M:	Jay Fang <f.fangjian@huawei.com>
+M:	Yang Shen <shenyang39@huawei.com>
 L:	linux-spi@vger.kernel.org
 S:	Maintained
 W:	http://www.hisilicon.com
-- 
2.33.0

Re: [PATCH] MAINTAINERS: Update HiSilicon SPI Controller driver maintainer

[Mark Brown]

On Thu, 29 May 2025 14:14:06 +0800, Yang Shen wrote:
> Add Yang Shen as the maintainer of the HiSilicon SPI Controller driver,
> replacing Jay Fang.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] MAINTAINERS: Update HiSilicon SPI Controller driver maintainer
      commit: 3b5d1efc878adee4835165663297a75193343d37

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark