linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: samuel.holland@sifive.com,
	Paul Walmsley <paul.walmsley@sifive.com>,
	greentime.hu@sifive.com, linux-riscv@lists.infradead.org,
	green.wan@sifive.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update SiFive driver maintainers
Date: Fri, 16 Feb 2024 19:10:26 +0000	[thread overview]
Message-ID: <20240216-imposing-disband-b0fd6d0c67b8@spud> (raw)
In-Reply-To: <mhng-a672acb9-4e32-4a63-898d-08b10d09d8b8@palmer-ri-x1c9>


[-- Attachment #1.1: Type: text/plain, Size: 3809 bytes --]

On Fri, Feb 16, 2024 at 10:43:31AM -0800, Palmer Dabbelt wrote:
> On Thu, 15 Feb 2024 15:49:11 PST (-0800), samuel.holland@sifive.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@sifive.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@sifive.com>
> > +M:	Samuel Holland <samuel.holland@sifive.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@sifive.com>
> >  M:	Greentime Hu <greentime.hu@sifive.com>
> > +M:	Samuel Holland <samuel.holland@sifive.com>
> >  L:	linux-pci@vger.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@dabbelt.com>
> >  M:	Paul Walmsley <paul.walmsley@sifive.com>
> > +M:	Samuel Holland <samuel.holland@sifive.com>
> >  L:	linux-riscv@lists.infradead.org
> >  S:	Supported
> > +F:	drivers/dma/sf-pdma/
> >  N:	sifive
> > +K:	fu[57]40
> >  K:	[^@]sifive
> > 
> > -SIFIVE CACHE DRIVER
> > -M:	Conor Dooley <conor@kernel.org>
> > -L:	linux-riscv@lists.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@sifive.com>
> > -M:	Palmer Dabbelt <palmer@dabbelt.com>
> > -L:	linux-riscv@lists.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@sifive.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@redhat.com>
> >  L:	linux-input@vger.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@rivosinc.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.

I don't think anything in this patch was "supposed" to go via the riscv
tree as things stood. Probably more a case of harassing subsystem
maintainers (or sending them PRs) than sending things to Arnd I think.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-02-16 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 23:49 [PATCH] MAINTAINERS: Update SiFive driver maintainers Samuel Holland
2024-02-16  0:43 ` Paul Walmsley
2024-02-16  9:37 ` Conor Dooley
2024-02-16 18:43 ` Palmer Dabbelt
2024-02-16 19:10   ` Conor Dooley [this message]
2024-02-27 10:08 ` Conor Dooley
2024-02-29 18:20 ` patchwork-bot+linux-riscv

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=20240216-imposing-disband-b0fd6d0c67b8@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=green.wan@sifive.com \
    --cc=greentime.hu@sifive.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.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 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).