linux-kernel - Re: [ANNOUNCE] scsi patch queue 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]

Date:	Wed, 21 May 2014 09:46:36 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Hannes Reinecke <hare@...e.de>, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree

Hi Christoph,

On Mon, 19 May 2014 22:39:28 -0700 Christoph Hellwig <hch@...radead.org> wrote:
>
> On Tue, May 20, 2014 at 10:03:43AM +1000, Stephen Rothwell wrote:
> > Is this a request for inclusion of those branches into linux-next
> > separately from the scsi tree itself?
> 
> James said he wants to include it in the scsi tree, but given how late
> we are in the cycle I'd love to see separate exposure until that happens
> on a temporary basis.

OK, I have added them from today (called scsi-core and scsi-drivers).
James, feel free to yell if that is not OK.  If these are to stay
longer term (and I have no objections given your list of requirements),
then you should rename the branches (maybe to -next instead of -3.16).

These will be merged after the scsi tree so that they effectively
disappear from my radar when they have been merged into James' tree.

Currently you are the only contact for problems - let me know if I
should add someone else (or a list).

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 branches 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 James (or ask him
to fetch).  They are 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)