Thread (79 messages) 79 messages, 17 authors, 2023-02-13

Re: remove arch/sh

From: Stephen Rothwell <hidden>
Date: 2023-02-05 23:09:12
Also in: alsa-devel, dmaengine, dri-devel, linux-arch, linux-devicetree, linux-gpio, linux-i2c, linux-input, linux-media, linux-mmc, linux-renesas-soc, linux-rtc, linux-serial, linux-sh, linux-spi, linux-usb, linux-watchdog, lkml, netdev

Hi,

On Fri, 3 Feb 2023 09:30:37 +0100 Christoph Hellwig [off-list ref] wrote:
On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
quoted
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
And by "Stephen", Christoph means me.  When you are ready, please send
me a request to include your tree/branch in linux-next (usually the
branch is called something like "for-next" or just "next") telling me
the git URL, and the contacts I should send email to if there are
conflicts/build issues with the branch.  I will then fetch the branch
every time I create a new linux-next release (most work days), so all
you need to do is update that branch each time you are ready to publish
more commits.

-- 
Cheers,
Stephen Rothwell

Attachments

  • (unnamed) [application/pgp-signature] 488 bytes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help