linux-kernel - Re: linux-next: build failure after merge of the l2-mtd tree

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: <20140527095942.0a071e63@canb.auug.org.au>
Date:	Tue, 27 May 2014 09:59:42 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Brian Norris <computersforpeace@...il.com>
Cc:	Artem Bityutskiy <dedekind1@...il.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Vincenzo Aliberti <vincenzo.aliberti@...il.com>
Subject: Re: linux-next: build failure after merge of the l2-mtd tree

Hi Brian,

On Mon, 26 May 2014 10:42:25 -0700 Brian Norris <computersforpeace@...il.com> wrote:
>
> On Thu, May 22, 2014 at 03:30:47PM +1000, Stephen Rothwell wrote:
> > Hi Artem,
> 
> FYI, I'm managing this tree now, not Artem.

OK, noted.  Is there a different URL for the tree as well?  Currently
it is git://git.infradead.org/users/dedekind/l2-mtd-2.6.git#master .

Here is the legalese:

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" (837 bytes)