linux-kernel - Re: Please add the tiny tree to 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: <20140923083442.15400844@canb.auug.org.au>
Date:	Tue, 23 Sep 2014 08:34:42 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Please add the tiny tree to linux-next

Hi Josh,

On Mon, 22 Sep 2014 10:53:04 -0700 Josh Triplett <josh@...htriplett.org> wrote:
>
> Can you please add the tiny tree, branch tiny/next of
> https://git.kernel.org/pub/scm/linux/kernel/git/josh/linux.git , to
> linux-next?
> 
> I'll be using this tree to upstream various patches for Linux kernel
> tinification.  I plan to use topic branches under tiny/* for separate
> topics, typically based on the previous -rc1, merging them into
> tiny/next; when the merge window opens, I'll submit a pull request for
> tiny/next and start merging new tiny/* topic branches into a
> tiny/next-next branch or similar that will become the new tiny/next
> after tiny/next gets merged.

Added from today.  I used git:// instead of https:// for the URL.

I do not want code for release N in linux-next until after (N-1)-rc1
has been released.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)