Re: [PATCH v3 7/8] MAINTAINERS: Add entry for MIPS RISC-V SoC support
From: Conor Dooley
Date: Wed Nov 18 2026 - 12:33:59 EST
On Wed, Nov 18, 2026 at 02:23:39PM +0000, Aleksa Paunovic wrote:
> Hi Conor,
>
> On 11/16/26 18:40, Conor Dooley wrote:
> >> From: Aleksa Paunovic <aleksa.paunovic@xxxxxxxxxxxxx>
> >>
> >> Add a MAINTAINERS entry covering the MIPS RISC-V devicetree sources
> >> and the board binding.
> >>
> >> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@xxxxxxxxxxxxx>
> >> ---
> >> MAINTAINERS | 7 +++++++
> >> 1 file changed, 7 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index c2414447892c24d58595059ca27b18775919ac12..a00f1a801be3c532c33918e673c7977d9de91823 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -23542,6 +23542,13 @@ F: drivers/spi/spi-mpfs.c
> >> F: drivers/usb/musb/mpfs.c
> >> F: include/soc/microchip/mpfs.h
> >>
> >> +RISC-V MIPS SoC SUPPORT
> >> +M: Aleksa Paunovic <aleksa.paunovic@xxxxxxxxxxxxx>
> >> +L: linux-riscv@xxxxxxxxxxxxxxxxxxx
> >> +S: Supported
> >> +F: Documentation/devicetree/bindings/riscv/mips.yaml
> >> +F: arch/riscv/boot/dts/mips/
> > Right, so still no git tree here. How are we going to get this applied? My comment on the last version was: | You're missing a MAINTAINERS entry for the platform, since someone is | going to have to pick up the patches for the arch/riscv/boot/dts/gf and | that someone is neither Palmer nor Paul. | See Documentation/process/maintainer-soc.rst for more info. | | I'd apply patches as a very last resort, but even then you'd need an entry | to make sure that you're CCed on patches for the platform because I | don't care about the platform and would just apply things that look | correct if there was no reviews provided. You have added the entry, which is great, but the absence of a git tree implies you're not actually intending applying the patches? Ideally you, someone that cares for this platform, would do that - and the lack of a tree implies that you're expecting someone else (me?) to do it. Cheers, Conor.
> I was planning on updating that later once we've decided which tree to use. I'll fix that in v4.
Cool, thanks!
Attachment:
signature.asc
Description: PGP signature