linux-kernel - Re: Request for linux-kselftest nolibc branch Inclusion in linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230725094219.7c1790fa@canb.auug.org.au>
Date:   Tue, 25 Jul 2023 09:42:19 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Shuah Khan <skhan@...uxfoundation.org>
Cc:     linux-next@...r.kernel.org,
        "Paul E. McKenney" <paulmck@...nel.org>, Willy Tarreau <w@....eu>,
        thomas@...ch.de, linux-kernel@...r.kernel.org,
        shuah <shuah@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Request for linux-kselftest nolibc branch Inclusion in
 linux-next

Hi Shuah,

On Mon, 24 Jul 2023 16:22:16 -0600 Shuah Khan <skhan@...uxfoundation.org> wrote:
>
> Please include the following linux-kselftest nolibc branch for linux-next
> coverage. This will be based on Linus's tree.
> 
> I will be using this branch to send nolibc pull requests to Linus.
> 
> URL for the branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=nolibc
> 
> Primary Contacts:
> Shuah Khan - shuah@...nel.org or Shuah Khan <skhan@...uxfoundation.org>
> 
> Please cc:
> Willy Tarreau <w@....eu>
> Thomas Weißschuh <thomas@...ch.de>
> Paul E. McKenney <paulmck@...nel.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@...b.auug.org.au

Content of type "application/pgp-signature" skipped