Re: Add thead to linux-next

[Stephen Rothwell <sfr@canb.auug.org.au>]

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

Hi Drew,

On Fri, 12 Jul 2024 21:35:20 -0700 Drew Fustini <drew@pdp7.com> wrote:
>
> I've taken over the maintainer role for for T-Head SoCs [1] and I've
> set up a tree that I will being using to send pull requests to Arnd.
> 
> Please add these branches to linux-next:
> 
> thead-dt-fixes git https://github.com/pdp7/linux.git#thead-dt-fixes
> thead-dt-for-next git https://github.com/pdp7/linux.git#thead-dt-for-next
> 
> Thanks,
> Drew
> 
> [1] https://lore.kernel.org/linux-riscv/20240620162522.386-1-jszhang@kernel.org/

Added from today.

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

-- 
Cheers,
Stephen Rothwell

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