linux-kernel - Re: [PATCH] MAINTAINERS: Update SiFive driver maintainers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 16 Feb 2024 10:43:31 -0800 (PST)
From: Palmer Dabbelt <palmer@...belt.com>
To: samuel.holland@...ive.com
CC: Conor Dooley <conor@...nel.org>, Paul Walmsley <paul.walmsley@...ive.com>,
  greentime.hu@...ive.com, linux-riscv@...ts.infradead.org, green.wan@...ive.com,
  samuel.holland@...ive.com, aou@...s.berkeley.edu, linux-kernel@...r.kernel.org
Subject:     Re: [PATCH] MAINTAINERS: Update SiFive driver maintainers

On Thu, 15 Feb 2024 15:49:11 PST (-0800), samuel.holland@...ive.com wrote:
> Add myself as a maintainer for the various SiFive drivers, since I have
> been performing cleanup activity on these drivers and reviewing patches
> to them for a while now. Remove Palmer as a maintainer, as he is focused
> on overall RISC-V architecture support.
>
> Collapse some duplicate entries into the main SiFive drivers entry:
>  - Conor is already maintainer of standalone cache drivers as a whole,
>    and these files are also covered by the "sifive" file name regex.
>  - Paul's git tree has not been updated since 2018, and all file names
>    matching the "fu540" pattern also match the "sifive" pattern.
>  - Green has not been active on the LKML for a couple of years.
>
> Signed-off-by: Samuel Holland <samuel.holland@...ive.com>
> ---
>
>  MAINTAINERS | 29 +++++------------------------
>  1 file changed, 5 insertions(+), 24 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 73d898383e51..f1bbb0f82664 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1395,6 +1395,7 @@ F:	drivers/hwmon/max31760.c
>
>  ANALOGBITS PLL LIBRARIES
>  M:	Paul Walmsley <paul.walmsley@...ive.com>
> +M:	Samuel Holland <samuel.holland@...ive.com>
>  S:	Supported
>  F:	drivers/clk/analogbits/*
>  F:	include/linux/clk/analogbits*
> @@ -16725,6 +16726,7 @@ F:	drivers/pci/controller/dwc/*layerscape*
>  PCI DRIVER FOR FU740
>  M:	Paul Walmsley <paul.walmsley@...ive.com>
>  M:	Greentime Hu <greentime.hu@...ive.com>
> +M:	Samuel Holland <samuel.holland@...ive.com>
>  L:	linux-pci@...r.kernel.org
>  S:	Maintained
>  F:	Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml
> @@ -19968,36 +19970,15 @@ S:	Maintained
>  F:	drivers/watchdog/simatic-ipc-wdt.c
>
>  SIFIVE DRIVERS
> -M:	Palmer Dabbelt <palmer@...belt.com>
>  M:	Paul Walmsley <paul.walmsley@...ive.com>
> +M:	Samuel Holland <samuel.holland@...ive.com>
>  L:	linux-riscv@...ts.infradead.org
>  S:	Supported
> +F:	drivers/dma/sf-pdma/
>  N:	sifive
> +K:	fu[57]40
>  K:	[^@]sifive
>
> -SIFIVE CACHE DRIVER
> -M:	Conor Dooley <conor@...nel.org>
> -L:	linux-riscv@...ts.infradead.org
> -S:	Maintained
> -F:	Documentation/devicetree/bindings/cache/sifive,ccache0.yaml
> -F:	drivers/cache/sifive_ccache.c
> -
> -SIFIVE FU540 SYSTEM-ON-CHIP
> -M:	Paul Walmsley <paul.walmsley@...ive.com>
> -M:	Palmer Dabbelt <palmer@...belt.com>
> -L:	linux-riscv@...ts.infradead.org
> -S:	Supported
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/pjw/sifive.git
> -N:	fu540
> -K:	fu540
> -
> -SIFIVE PDMA DRIVER
> -M:	Green Wan <green.wan@...ive.com>
> -S:	Maintained
> -F:	Documentation/devicetree/bindings/dma/sifive,fu540-c000-pdma.yaml
> -F:	drivers/dma/sf-pdma/
> -
> -
>  SILEAD TOUCHSCREEN DRIVER
>  M:	Hans de Goede <hdegoede@...hat.com>
>  L:	linux-input@...r.kernel.org

I'm fine not having to maintain the SiFive drivers, the SOC stuff was 
never really my thing anyway so that's all a bit easier on my end.  So

Acked-by: Palmer Dabbelt <palmer@...osinc.com>

I do end up picking up some random patches though, mostly because stuff 
seems to slip through the cracks.  Are you going to have an SOC subtree 
and send stuff over there?  That seems more manageable on my end, as 
it's a bit scattered today.