linux-kernel - Re: A few tree inclusion update requests

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]

Date:	Tue, 13 Apr 2010 09:46:18 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux Next <linux-next@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: A few tree inclusion update requests

Hi Frederic,

On Sat, 10 Apr 2010 15:42:23 +0200 Frederic Weisbecker <fweisbec@...il.com> wrote:
>
> I have some requests for you about tree inclusions for linux-next.
> 
> My reiserfs/kill-bkl branch had no updates for a next release
> for some time now. You can safely remove it from -next. If
> I get updates for it later, I'll tell you. But for now it's
> only here to host fixes for the current release.

There is some value to having "fixes for the current release" trees in
linux-next - it means that while such fixes are waiting for Linus to
merge them, people testing linux-next don't have to worry about bugs that
already have fixes pending.  However, I have removed that tree - I will
put it back if you ask me to.

> Also I have two new branches aimed for .35
> 
> Could you please integrate the two following?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> 	bkl/core
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> 	bkl/procfs

Both added from today.

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