From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755388AbaEPWBZ (ORCPT ); Fri, 16 May 2014 18:01:25 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:46583 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754854AbaEPWBX (ORCPT ); Fri, 16 May 2014 18:01:23 -0400 Message-ID: <1400277676.16968.2.camel@dabdike.int.hansenpartnership.com> Subject: Re: SCSI "staging" tree for linux-next? From: James Bottomley To: Hannes Reinecke Cc: Christoph Hellwig , Stephen Rothwell , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 16 May 2014 15:01:16 -0700 In-Reply-To: <537614CC.6020602@suse.de> References: <20140515052645.GA26266@infradead.org> <537614CC.6020602@suse.de> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.12.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2014-05-16 at 15:38 +0200, Hannes Reinecke wrote: > On 05/15/2014 07:26 AM, Christoph Hellwig wrote: > > Hi James, > > > > we're past -rc5 and no SCSI patches have been collected for 3.16 yet, > > despite a lot of patches including a lot of reviewed ones pending on the > > list. > > > > I'd really love to get at least some testing for all the work that > > sometimes has been pending for months in linux-next and would offer to > > put together a tree of reviewed patches for linux-next. Is this fine > > with you? > > > Seconded. Having a staging tree would make my life _so_ much easier. OK, I think we can do this easily. Send me your staging branches and I'll pull them into a global staging branch and merge it with for-next in linux-scsi ... this will ensure we don't get yelled at for duplicate commits causing merge rejections in linux-next. Since staging will be volatile and for the purposes of testing patches on upstream track, we don't need signed tags or anything. James