Hi Arnd! On Mon, 2023-12-18 at 20:52 +0000, Arnd Bergmann wrote: > > My SPARC experience is mainly with > > SPARC32 rather than SPARC64, so discussing a co-maintainership with a > > SPARC32 focus would feel natural as a start. I do not have much in terms > > of SPARC64 or non-LEON SPARC32 hardware available for testing. > > I think that's all we need at the moment. The lack of an active > maintainer does get in the way of cross-architecture work, > especially when touching the oldest parts of the code. Fully agreed. > The most important bit here would be someone with the authority > or Ack or Nak a patch going into another git tree. Even if you > are sometimes wrong, that is still much better than no reply. Yep. And there are actually a number of very nice improvements from Oracle engineers for sparc64 that got never upstreamed. These include kexec support as well as support for hypervisor control from Linux. They can all be found in Oracle's Unbreakable Kernel Tree: > https://github.com/oracle/linux-uek/tree/uek4/qu7 I have already reached out to one of the Oracle engineers and they would be happy to help us getting some of the patches merged upstream. > On top of that it would be good if you can set up a git tree > for collecting patches to forward to Linus and get included > in linux-next, in place of Dave's orphaned sparc.git. > Once you have an entry in the MAINTAINERS file, you can ask > for an account to host this on git.kernel.org, but other > locations are also fine if you already have something we can > put in the MAINTAINERS entry. > > Do you have a preferred place to host a tree? I would choose the same path that I took for arch/sh. Add Andreas as a maintainer for arch/sparc to MAINTAINERS and then grant access to kernel.org so he can create his tree there. This makes sure that the tree can be easily located by anyone else and also get lost because of an external repository becoming unavailable. > > Has someone reached out to Dave? I think discussions like these might > > be better served in a thread of its own. > > As far as I can tell, Dave has focused mainly on networking and > bpf development rather than sparc for a few years now. Good to know. > I would suggest that I send him a proposed update to the MAINTAINERS > file with both of you listed as maintainers and ideally your git > tree location replacing his. > > Dave can then reply if he has any other preferences (e.g. having > separate sparc32 and sparc64 maintainers, or becoming reviewer > instead of maintainer). I think promoting Andreas as the second maintainer would be an ideal solution. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
