mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Hannes Reinecke <hare@suse.de>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Tue, 20 May 2014 10:03:43 +1000	[thread overview]
Message-ID: <20140520100343.31490551@canb.auug.org.au> (raw)
In-Reply-To: <20140519140614.GA12183@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

Hi Christoph,

On Mon, 19 May 2014 07:06:14 -0700 Christoph Hellwig <hch@infradead.org> wrote:
>
> 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.

Is this a request for inclusion of those branches into linux-next
separately from the scsi tree itself?

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-20  0:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 14:06 Christoph Hellwig
2014-05-20  0:03 ` Stephen Rothwell [this message]
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-11 12:01 ` Christoph Hellwig
2014-06-11 14:17   ` James Bottomley
2014-06-11 14:31     ` 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=20140520100343.31490551@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --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

Powered by JetHome