All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@lst.de>
Cc: lsf@lists.linux-foundation.org,
	lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: Re: [TOPIC] scsi-queue tree past and future
Date: Thu, 05 Mar 2015 06:48:08 -0800	[thread overview]
Message-ID: <1425566888.2169.17.camel@HansenPartnership.com> (raw)
In-Reply-To: <20150305133118.GA16575@lst.de>

On Thu, 2015-03-05 at 14:31 +0100, Christoph Hellwig wrote:
> For about 8 month I've merged almost every scsi commit through the
> scsi-queue staging tree, and it seems to have worked out well enough.
> 
> I've been too busy for the next cycle, so 4.1 will probably have to live
> without it.  I'd like to get feedback on how the tree worked for contributors
> and driver maintainers, and brainstorm how to move forward with it, preferably
> some form of real team maintainance that avoids single points of failure.

I'd like to thank Christoph for doing this, it's been an enormous help.

Here's what we'll do for 4.1: I need all the current Maintainers to
collect the patches and reviews in their area and send them to the list
as a series.  We'll be adhering to the guidelines Christoph laid down
for inclusion:

 - the patch needs at least two positive reviews (non-author signoff,
   reviewed-by or acked-by tags).   In practice this means it had at
   least one and I added another one.
   As an exception I also take trivial and important fixes if they
   only have a Tested-by: instead of a second review.
 - the patch has no negative review on the mailing list
 - the patch applies cleanly
 - the patch compiles (drivers for architectures I can't test excluded)
 - for core the core branch: the patch survives a full xfstests run

For the last requirement, the 0 day kernel test project will be checking
this.  That means negative reports from the 0 day project on a patch
will be grounds for removal.

I'll try to curate the patches in areas without maintainers (like the
core).  Remember, in all cases, you get an email from my automation
infrastructure when a patch is added (or removed) from any of the SCSI
trees, so if you haven't seen the email, the patch isn't in the tree.

You can also see the state of the git trees here:

http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/

with the misc branch being for 4.1 and the fixes branch being for 4.0-rc

James



  reply	other threads:[~2015-03-05 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 13:31 [TOPIC] scsi-queue tree past and future Christoph Hellwig
2015-03-05 14:48 ` James Bottomley [this message]
2015-03-07  4:22   ` [Lsf] " Davidlohr Bueso
2015-03-07  4:43     ` James Bottomley
2015-03-07  4:47       ` Davidlohr Bueso
2015-03-07  3:10 ` Sagi Grimberg
2015-03-10 12:37 ` Tomas Henzl

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=1425566888.2169.17.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.