MAINTAINERS: setup support for SpacemiT SoC tree

Commit Message

Yixun Lan Oct. 23, 2024, 4:18 a.m. UTC

Add myself as maintainer of SpacemiT's SoC tree, which
suggested by Conor [1].

Link: https://lore.kernel.org/all/20241018234615-GYA2124001@gentoo/ [1]
Signed-off-by: Yixun Lan <[e-mail]>
---
This will setup proper maintainer info about Spacemit's kernel tree,
which should help to take soc and device tree patches, and send the
pull request up to Arnd's soc tree.

I asked Kevin to host the kernel tree under SpacemiT's account
on github, which should help people to get access more easily,
and promote the tree a little bit.

I could take this patch through this spacemit's soc tree if no objection,
of cource, after got ACK.
---
 MAINTAINERS | 9 +++++++++
 1 file changed, 9 insertions(+)


---
base-commit: 42f7652d3eb527d03665b09edac47f85fb600924
change-id: 20241023-00-k1-maintainer-46eb3f31e6f2

Best regards,

Comments

Conor Dooley Oct. 24, 2024, 3:31 p.m. UTC | #1

On Wed, Oct 23, 2024 at 12:18:19PM +0800, Yixun Lan wrote:
> Add myself as maintainer of SpacemiT's SoC tree, which
> suggested by Conor [1].
> 
> Link: https://lore.kernel.org/all/20241018234615-GYA2124001@gentoo/ [1]
> Signed-off-by: Yixun Lan <[e-mail]>
> ---
> This will setup proper maintainer info about Spacemit's kernel tree,
> which should help to take soc and device tree patches, and send the
> pull request up to Arnd's soc tree.
> 
> I asked Kevin to host the kernel tree under SpacemiT's account
> on github, which should help people to get access more easily,
> and promote the tree a little bit.

What do you mean by "get access more easily"?

In case it is not clear, noone other than those listed in the
maintainers entry should be pushing content to the fixes/next
branches and all patches must go through the mailing lists and review
process. I'm sure you're well aware of this, but I've never interacted
with spacemit and don't know if they are.

Make sure you add the fixes/next branches to linux-next when you have
the branches established.

> I could take this patch through this spacemit's soc tree if no objection,
> of cource, after got ACK.

Yes, do it along with the base series, when that goes in.

> ---
>  MAINTAINERS | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e9659a5a7fb3347d649855992a559e3526d18443..4087023593f7a0b2d5c5827df682230c329f82a9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19791,6 +19791,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/
>  X:	arch/riscv/boot/dts/thead/

Huh, this is not meant to look like that. Looks like the patch went
missing. I'll have to rectify that. You can drop this hunk. I'm going
to invert it:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/commit/?h=riscv-soc-fixes

>  
>  RISC-V PMU DRIVERS
> @@ -21578,6 +21579,14 @@ W:	https://linuxtv.org
>  Q:	http://patchwork.linuxtv.org/project/linux-media/list/
>  F:	drivers/media/dvb-frontends/sp2*
>  
> +SPACEMIT SoC Support
> +M:	Yixun Lan <[e-mail]>

I'd like to see someone else here, but if noone is volunteering
themselves, we can hardly force them!

> +S:	Maintained
> +T:	git https://github.com/spacemit-com/linux
> +F:	arch/riscv/boot/dts/spacemit/
> +N:	spacemit
> +K:	spacemit
> +
>  SPANISH DOCUMENTATION
>  M:	Carlos Bilbao <[e-mail]>
>  R:	Avadhut Naik <[e-mail]>
> 
> ---
> base-commit: 42f7652d3eb527d03665b09edac47f85fb600924
> change-id: 20241023-00-k1-maintainer-46eb3f31e6f2
> 
> Best regards,
> -- 
> Yixun Lan <[e-mail]>
>

Yixun Lan Oct. 24, 2024, 8:44 p.m. UTC | #2

Hi Conor:

once more thing, I'd like to add one additonal mailinglist info,
which make sure all spacemit future patches flow to linux-riscv mailinglist

L: [e-mail]

let me know if this is not ok?

On 16:31 Thu 24 Oct     , Conor Dooley wrote:
> On Wed, Oct 23, 2024 at 12:18:19PM +0800, Yixun Lan wrote:
> > Add myself as maintainer of SpacemiT's SoC tree, which
> > suggested by Conor [1].
> > 
> > Link: https://lore.kernel.org/all/20241018234615-GYA2124001@gentoo/ [1]
> > Signed-off-by: Yixun Lan <[e-mail]>
> > ---
> > This will setup proper maintainer info about Spacemit's kernel tree,
> > which should help to take soc and device tree patches, and send the
> > pull request up to Arnd's soc tree.
> > 
> > I asked Kevin to host the kernel tree under SpacemiT's account
> > on github, which should help people to get access more easily,
> > and promote the tree a little bit.
> 
> What do you mean by "get access more easily"?
> 
I'd collect all patches of spacemit (including those sent by others)
and put them into a staging WIP branch, for people who interested to
download/test (not strongly related to upstream work..)

for not hosting the tree at my personal account, as I'd wish more
people to join as the maintainer, which would be easy to manage this..

> In case it is not clear, noone other than those listed in the
> maintainers entry should be pushing content to the fixes/next
> branches and all patches must go through the mailing lists and review
yes, I understand

> process. I'm sure you're well aware of this, but I've never interacted
> with spacemit and don't know if they are.
> 
yes, I will make sure them aware of this.

> Make sure you add the fixes/next branches to linux-next when you have
> the branches established.
> 
ok, I will send email to Stephen once this patch accepted

> > I could take this patch through this spacemit's soc tree if no objection,
> > of cource, after got ACK.
> 
> Yes, do it along with the base series, when that goes in.
> 
sure, will take it along with initial DT series

> > ---
> >  MAINTAINERS | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index e9659a5a7fb3347d649855992a559e3526d18443..4087023593f7a0b2d5c5827df682230c329f82a9 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -19791,6 +19791,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/
> >  X:	arch/riscv/boot/dts/thead/
> 
> Huh, this is not meant to look like that. Looks like the patch went
> missing. I'll have to rectify that. You can drop this hunk. I'm going
> to invert it:
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/commit/?h=riscv-soc-fixes
> 
ok
> >  
> >  RISC-V PMU DRIVERS
> > @@ -21578,6 +21579,14 @@ W:	https://linuxtv.org
> >  Q:	http://patchwork.linuxtv.org/project/linux-media/list/
> >  F:	drivers/media/dvb-frontends/sp2*
> >  
> > +SPACEMIT SoC Support
> > +M:	Yixun Lan <[e-mail]>
> 
> I'd like to see someone else here, but if noone is volunteering
> themselves, we can hardly force them!
> 
sure, let's give people some time to consider, and I will send an updated version
next week..

> > +S:	Maintained
> > +T:	git https://github.com/spacemit-com/linux
> > +F:	arch/riscv/boot/dts/spacemit/
> > +N:	spacemit
> > +K:	spacemit
> > +
> >  SPANISH DOCUMENTATION
> >  M:	Carlos Bilbao <[e-mail]>
> >  R:	Avadhut Naik <[e-mail]>
> > 
> > ---
> > base-commit: 42f7652d3eb527d03665b09edac47f85fb600924
> > change-id: 20241023-00-k1-maintainer-46eb3f31e6f2
> > 
> > Best regards,
> > -- 
> > Yixun Lan <[e-mail]>
> >

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index e9659a5a7fb3347d649855992a559e3526d18443..4087023593f7a0b2d5c5827df682230c329f82a9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19791,6 +19791,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/
 X:	arch/riscv/boot/dts/thead/
 
 RISC-V PMU DRIVERS
@@ -21578,6 +21579,14 @@  W:	https://linuxtv.org
 Q:	http://patchwork.linuxtv.org/project/linux-media/list/
 F:	drivers/media/dvb-frontends/sp2*
 
+SPACEMIT SoC Support
+M:	Yixun Lan <[e-mail]>
+S:	Maintained
+T:	git https://github.com/spacemit-com/linux
+F:	arch/riscv/boot/dts/spacemit/
+N:	spacemit
+K:	spacemit
+
 SPANISH DOCUMENTATION
 M:	Carlos Bilbao <[e-mail]>
 R:	Avadhut Naik <[e-mail]>