On Wed, 2014-05-21 at 09:46 +1000, Stephen Rothwell wrote: > Hi Christoph, > > On Mon, 19 May 2014 22:39:28 -0700 Christoph Hellwig <hch@xxxxxxxxxxxxx> 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. Let's try the process. > 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). I'll merge it into for-next in SCSI to make it easier. > 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). Also cc the scsi mailing list for merge problems, just in case. Thanks, James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
