linux-kernel - Re: cleancache into linux-next, target for 2.6.37 merge window?

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 29 Sep 2010 10:48:27 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: cleancache into linux-next, target for 2.6.37 merge window?

Hi Dan,

On Tue, 28 Sep 2010 12:31:18 -0700 (PDT) Dan Magenheimer <dan.magenheimer@...cle.com> wrote:
>
> The "cleancache" patchset crosses multiple subsystem boundaries and
> at the recent filesystem/storage/mm summit, people suggested that
> after the patchset has stabilized, I should just submit it to
> linux-next and then directly to Linus.  The latest version has received
> no further suggestions or comments.  Previous versions received
> a great deal of review and comment from a wide variety of maintainers
> across all the impacted subsystems, as documented in the commit logs.
> 
> Would it be possible to include the following tree in the linux-next
> build process?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/djm/tmem.git#linux-next

Included from today.  I have you as the contact (in case I have problems)
if there is any other address I should notify, just let me know.

> The patchset applies cleanly against both 2.6.36-rc3 and -rc5.
> Against next-20100928, I see two very minor merge conflicts in
> mm/Kconfig and include/linux/fs.h due to minor changes from other
> trees.

Thanks.  I will send notifications for those (just so you know) and will
fix them up.  Minor conflicts are not a problem and can be fixed by Linus
when he merges this tree (or the others that conflict).

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