Include in next: spacemit/linux

Include in next: spacemit/linux

[Yixun Lan]

Hi Stephen,

Please kindly include spacemit/linux tree into the linux-next:

https://github.com/spacemit-com/linux


branch for master: for-next

branch for pending-fixes: fixes

Repo will be use for collecting patches for SpacemiT's SoC
which recently I took over:

https://lore.kernel.org/r/20241028-00-k1-maintainer-v2-1-272c9834220d@gentoo.org

The patches in the tree will be sent to Arnd Bergmann and soc@kernel.org.

Best regards,

-- 
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55

Re: Include in next: spacemit/linux

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Hi,

On Tue, 29 Oct 2024 12:53:26 +0800 Yixun Lan <dlan@gentoo.org> wrote:
>
> Please kindly include spacemit/linux tree into the linux-next:
> 
> https://github.com/spacemit-com/linux
> 
> branch for master: for-next
> 
> branch for pending-fixes: fixes
> 
> Repo will be use for collecting patches for SpacemiT's SoC
> which recently I took over:
> 
> https://lore.kernel.org/r/20241028-00-k1-maintainer-v2-1-272c9834220d@gentoo.org
> 
> The patches in the tree will be sent to Arnd Bergmann and soc@kernel.org.

Added from tomorrow.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Include in next: spacemit/linux

[Yixun Lan]

Hi Stephen:

On 17:33 Tue 29 Oct     , Stephen Rothwell wrote:
> Hi,
> 
> On Tue, 29 Oct 2024 12:53:26 +0800 Yixun Lan <dlan@gentoo.org> wrote:
> >
> > Please kindly include spacemit/linux tree into the linux-next:
> > 
> > https://github.com/spacemit-com/linux
> > 
> > branch for master: for-next
> > 
> > branch for pending-fixes: fixes
> > 
> > Repo will be use for collecting patches for SpacemiT's SoC
> > which recently I took over:
> > 
> > https://lore.kernel.org/r/20241028-00-k1-maintainer-v2-1-272c9834220d@gentoo.org
> > 
> > The patches in the tree will be sent to Arnd Bergmann and soc@kernel.org.
> 
> Added from tomorrow.
> 
> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgement of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window. 
> 
> You will need to ensure that the patches/commits in your tree/series have
> been:
>      * submitted under GPL v2 (or later) and include the Contributor's
>         Signed-off-by,
>      * posted to the relevant mailing list,
>      * reviewed by you (or another maintainer of your subsystem tree),
>      * successfully unit tested, and 
>      * destined for the current or next Linux merge window.
> 
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.
> 
Yes, I understand and thanks for all the info..

-- 
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55