[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240617-margarita-alongside-255cbb09ef59@wendy>
Date: Mon, 17 Jun 2024 08:28:41 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Yangyu Chen <cyy@...self.name>
CC: Conor Dooley <conor@...nel.org>, Yixun Lan <dlan@...too.org>,
<linux-riscv@...ts.infradead.org>, Conor Dooley <conor+dt@...nel.org>, Palmer
Dabbelt <palmer@...belt.com>, Paul Walmsley <paul.walmsley@...ive.com>,
Samuel Holland <samuel.holland@...ive.com>, Anup Patel <anup.patel@....com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
<devicetree@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Jesse Taube <jesse@...osinc.com>
Subject: Re: [PATCH v1 0/9] riscv: add initial support for SpacemiT K1
On Mon, Jun 17, 2024 at 10:00:32AM +0800, Yangyu Chen wrote:
>
> > On Jun 17, 2024, at 06:48, Yixun Lan <dlan@...too.org> wrote:
> >
> > Hi Conor
> > Thanks for bringing this up
> >
> > On 19:35 Sun 16 Jun , Conor Dooley wrote:
> >> On Mon, Jun 17, 2024 at 01:18:52AM +0800, Yangyu Chen wrote:
> >>
> >> No MAINTAINERS update, so I figure that means you don't want to maintain
> >> it going forwards? If there's someone out that that does care about the
> >> spacemit k1 (Jesse maybe?), then I'd be more than happy to have them
> >> look after it.
>
> Actually, I don’t know how to be a maintainer. Should I have to
> provide a new git tree and all the new patches merged to my tree
> and then submit a git pull?
Yeah, in the ideal case :) I wrote a document with information as to
how this all works for new platform maintainers:
https://docs.kernel.org/process/maintainer-soc.html#information-for-new-submaintainers
> Or reuse the RISC-V mailing list and
> just give a review, and the patches come to soc misc tree? I would
> like the latter one.
If you don't have the time/interest/whatever in having a tree, then
sure, I can apply the patches for it. I'd rather have someone look after
a tree themselves, but this option is better than me growing another
platform to look after.
> > Yangyu kind of has limited time, too many stuff for him..
> >
>
> True. Maybe I can have a review and test the patch in one week.
> However, providing a review and test in 2-3 days is sometimes hard
> for me.
It would be unreasonable to expect a 2-3 day turnaround :)
> > I'd volunteered to help on this if it can fill the gap
> > Also I'd be more than happy if anyone willing step forward to co-maintain..
> >
>
> Thanks. Really appreciate it.
>
> Should I provide a diff like this:
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d6c90161c7bf..718d30996f12 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19306,6 +19306,7 @@ F: arch/riscv/boot/dts/
> X: arch/riscv/boot/dts/allwinner/
> X: arch/riscv/boot/dts/renesas/
> X: arch/riscv/boot/dts/sophgo/
> +X: arch/riscv/boot/dts/spacemit/
If you don't want to apply patches, drop this hunk.
> RISC-V PMU DRIVERS
> M: Atish Patra <atishp@...shpatra.org>
> @@ -21004,6 +21005,13 @@ W: https://linuxtv.org
> Q: http://patchwork.linuxtv.org/project/linux-media/list/
> F: drivers/media/dvb-frontends/sp2*
>
> +SPACEMIT DEVICETREES and DRIVERS
> +M: Yangyu Chen <cyy@...self.name>
> +M: Yixun Lan <dlan@...too.org>
Jesse mentioned on IRC she was interested in the platform, so maybe she
would like to be involved too.
Thanks,
Conor.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists