linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Hannes Reinecke <hare@suse.de>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] scsi patch queue tree
Date: Mon, 19 May 2014 07:06:14 -0700	[thread overview]
Message-ID: <20140519140614.GA12183@infradead.org> (raw)

I'd like to announce the new scsi patch queue tree, which will pick up
any scsi core or driver patches promptly to allow easy integration and
feedback that contributors might be used to from other kernel subsystems.

There are two branches, one for the SCSI core and upper level drivers,
and one for low-level (hardware) drivers:

  git://git.infradead.org/users/hch/scsi-queue.git core-for-3.16
  git://git.infradead.org/users/hch/scsi-queue.git drivers-for-3.16 

The rules for the tree are:

 - it has 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.
 - no negative review on the mailing list
 - it applies cleanly
 - it compiles cleanly (drivers for architectures I can't test excluded)
 - for core the core branch: survives a full xfstests run

I went through the linux-scsi archives for March, April and May and
applied all patches that clearly fit the above criteria, but it's fairly
like I missed some.

If I'm missing your patch(es):

 - resend it unless it was sent in the last few weeks
 - make sure all reviews are recorded in the most recent post of the
   patch(es)
 - ping the list for additional reviewers

For now the prime intent of the tree is to feed it to James, although
I'd welcome everyone interested to pull and test it.  If the scheme
proves successful I'd love to invite more core scsi contributors to help
with it and move to a shared kernel.org tree.

             reply	other threads:[~2014-05-19 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 14:06 Christoph Hellwig [this message]
2014-05-20  0:03 ` [ANNOUNCE] scsi patch queue tree Stephen Rothwell
2014-05-20  5:39   ` Christoph Hellwig
2014-05-20 23:46     ` Stephen Rothwell
2014-05-21  2:25       ` James Bottomley
2014-05-28 10:54         ` Christoph Hellwig
2014-05-28 15:37           ` Mike Christie
2014-05-28 15:50             ` Christoph Hellwig
2014-05-28 16:04               ` Mike Christie
2014-05-28 16:05                 ` Christoph Hellwig
2014-05-28 16:01           ` Sujit Reddy Thumma
2014-05-28 16:03             ` Christoph Hellwig
2014-06-02  7:58           ` Christoph Hellwig
2014-06-02  8:25             ` Boaz Harrosh
2014-06-02  8:26               ` Christoph Hellwig
2014-06-02  8:32                 ` Boaz Harrosh
2014-06-11 12:01 ` Christoph Hellwig
2014-06-11 14:17   ` James Bottomley
2014-06-11 14:31     ` Christoph Hellwig
2014-06-24 15:52       ` Christoph Hellwig
2014-06-24 15:53         ` Christoph Hellwig
2014-06-25 12:41           ` 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=20140519140614.GA12183@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).