Hi-- On 2/3/23 02:33, Geert Uytterhoeven wrote: > Hi Adrian, > > On Fri, Feb 3, 2023 at 11:29 AM John Paul Adrian Glaubitz > <glaubitz@xxxxxxxxxxxxxxxxxxx> wrote: >> On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote: >>> On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote: >>>> Since this is my very first time stepping up as a kernel maintainer, I was hoping >>>> to get some pointers on what to do to make this happen. >>>> >>>> So far, we have set up a new kernel tree and I have set up a local development and >>>> test environment for SH kernels using my SH7785LCR board as the target platform. >>>> >>>> Do I just need to send a patch asking to change the corresponding entry in the >>>> MAINTAINERS file? >>> >>> I'm not sure a there is a document, but: >>> >>> - add the MAINTAINERS change to your tree >>> - ask Stephen to get your tree included in linux-next >>> >>> then eventually send a pull request to Linus with all of that. Make >>> sure it's been in linux-next for a while. >> >> OK, thanks for the pointers! Will try to get this done by next week. >> >> We're still discussing among SuperH developer community whether there will be a second >> maintainer, so please bear with us a few more days. I will collect patches in the >> meantime. > > Thanks a lot! > > If you need any help with process, setup, ... don't hesitate to ask > (on e.g. #renesas-soc on Libera). While Adrian and Geert are reading this, I have a question: Is this "sh64" still accurate and applicable? from Documentation/kbuild/kbuild.rst: But some architectures such as x86 and sparc have aliases. - x86: i386 for 32 bit, x86_64 for 64 bit - sh: sh for 32 bit, sh64 for 64 bit <<<<<<<<<<<<<<< - sparc: sparc32 for 32 bit, sparc64 for 64 bit Thanks. -- ~Randy
