linux-kernel - Re: linux-next: New trees

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] [day] [month] [year] [list]

Message-Id: <20130125102036.c04539e1b0beb2f44f8394cd@canb.auug.org.au>
Date:	Fri, 25 Jan 2013 10:20:36 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Steffen Klassert <steffen.klassert@...unet.com>
Cc:	David Miller <davem@...emloft.net>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: linux-next: New trees - ipsec and ipsec-next

Hi Steffen,

On Thu, 24 Jan 2013 07:13:15 +0100 Steffen Klassert <steffen.klassert@...unet.com> wrote:
>
> could you please add the ipsec and ipsec-next tree to linux-next?
> 
> The ipsec tree is intended to cover fixes for the ipsec networking
> subsystem and the ipsec-next tree to cover changes for ipsec with
> linux-next as target.
> 
> The trees are located at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git master
> git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
> 
> The ipsec tree follows David Miller's net tree, the ipsec-next tree follows
> the net-next tree. So they should be merged after net and net-next.

Added from today with just you as the contact.

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

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped