[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140519140614.GA12183@infradead.org>
Date: Mon, 19 May 2014 07:06:14 -0700
From: Christoph Hellwig <hch@...radead.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Hannes Reinecke <hare@...e.de>, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [ANNOUNCE] scsi patch queue tree
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists