linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] scsi patch queue tree updated
Date: Tue, 30 Dec 2014 05:02:30 -0800	[thread overview]
Message-ID: <20141230130230.GA28717@infradead.org> (raw)
In-Reply-To: <20140708134003.GA7790@infradead.org>

It turnd out while the scsi-queue tree in general worked very well
the split into core and drivers branches was rather cumbersome.

For the 3.19 merge window updates and the 3.20 window I've switched
to a single branch instead:

   git://git.infradead.org/users/hch/scsi-queue.git scsi-for-3.19
   git://git.infradead.org/users/hch/scsi-queue.git scsi-for-3.20

So far there 3.20 tree is still rather small, but there are a couple
of series that need a resend or review and should go in.

The rules from the original scsi-queue tree have worked well, so they
still apply with a minor change.  These rules are:

 - 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

  parent reply	other threads:[~2014-12-30 13:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 13:40 [ANNOUNCE] scsi patch queue tree updated Christoph Hellwig
2014-08-01 12:20 ` Christoph Hellwig
2014-08-01 20:32   ` James Bottomley
2014-08-04 11:11     ` Christoph Hellwig
2014-08-04 11:30       ` Stephen Rothwell
2014-08-04 11:34         ` Christoph Hellwig
2014-08-04 11:39           ` Stephen Rothwell
2014-08-04 14:20       ` James Bottomley
2014-08-14 12:54         ` Christoph Hellwig
2014-08-14 17:47           ` James Bottomley
2014-08-15 19:25             ` Christoph Hellwig
2014-08-15 19:32               ` James Bottomley
2014-09-15 22:58   ` Christoph Hellwig
2014-09-16 21:37     ` Christoph Hellwig
2014-09-16 21:44       ` James Bottomley
2014-12-30 13:02 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-18 10:02 Christoph Hellwig
2014-07-25 21:19 ` Christoph Hellwig

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=20141230130230.GA28717@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).