Add crc-next tree to linux-next

Add crc-next tree to linux-next

[Eric Biggers]

Hi Stephen,

When you have a chance, can you please add the following to linux-next:

    Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
    Branch: crc-next
    Contacts: Eric Biggers <ebiggers@kernel.org>

Thanks!

- Eric

Re: Add crc-next tree to linux-next

[Mark Brown]

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

On Sun, Dec 01, 2024 at 05:31:54PM -0800, Eric Biggers wrote:
> Hi Stephen,
> 
> When you have a chance, can you please add the following to linux-next:
> 
>     Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
>     Branch: crc-next
>     Contacts: Eric Biggers <ebiggers@kernel.org>

I'll pull this in to the builds I'm doing this week, you should check
that Stephen also adds it.  It's likely that he'll put it in at a
different point in the merge too, though hopefully that won't cause any
issues.

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.

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

Re: Add crc-next tree to linux-next

[Stephen Rothwell]

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

Hi Eric,

On Sun, 1 Dec 2024 17:31:54 -0800 Eric Biggers <ebiggers@kernel.org> wrote:
>
> When you have a chance, can you please add the following to linux-next:
> 
>     Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
>     Branch: crc-next
>     Contacts: Eric Biggers <ebiggers@kernel.org>

Added to my tree form today (Mark added it to his last week).

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 --]