mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: SCSI "staging" tree for linux-next?
Date: Fri, 16 May 2014 15:01:16 -0700	[thread overview]
Message-ID: <1400277676.16968.2.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <537614CC.6020602@suse.de>

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



  parent reply	other threads:[~2014-05-16 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  5:26 Christoph Hellwig
2014-05-16 13:38 ` Hannes Reinecke
2014-05-16 21:39   ` Nicholas A. Bellinger
2014-05-16 22:01   ` James Bottomley [this message]
2014-05-19  0:20     ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1400277676.16968.2.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®