Request to add linux-kselftest kunit-fixes branch to linux-next

Request to add linux-kselftest kunit-fixes branch to linux-next

[Shuah Khan]

Please add kunit-fixes branch to linux-next.


https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=kunit-fixes


Contacts:

Shuah Khan
Brendan Higgins

thanks,
-- Shuah

Re: Request to add linux-kselftest kunit-fixes branch to linux-next

[Stephen Rothwell]

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

Hi Shuah,

On Fri, 26 Jun 2020 14:50:25 -0600 Shuah Khan <skhan@linuxfoundation.org> wrote:
>
> Please add kunit-fixes branch to linux-next.
> 
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=kunit-fixes
> 
> 
> Contacts:
> 
> Shuah Khan
> Brendan Higgins

Added from Monday.

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