From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Wed, 21 May 2014 11:25:01 +0900 [thread overview]
Message-ID: <1400639101.2481.19.camel@dabdike> (raw)
In-Reply-To: <20140521094636.515289e8@canb.auug.org.au>
On Wed, 2014-05-21 at 09:46 +1000, Stephen Rothwell wrote:
> Hi Christoph,
>
> On Mon, 19 May 2014 22:39:28 -0700 Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Tue, May 20, 2014 at 10:03:43AM +1000, Stephen Rothwell wrote:
> > > Is this a request for inclusion of those branches into linux-next
> > > separately from the scsi tree itself?
> >
> > James said he wants to include it in the scsi tree, but given how late
> > we are in the cycle I'd love to see separate exposure until that happens
> > on a temporary basis.
>
> OK, I have added them from today (called scsi-core and scsi-drivers).
> James, feel free to yell if that is not OK.
Let's try the process.
> If these are to stay
> longer term (and I have no objections given your list of requirements),
> then you should rename the branches (maybe to -next instead of -3.16).
I'll merge it into for-next in SCSI to make it easier.
> These will be merged after the scsi tree so that they effectively
> disappear from my radar when they have been merged into James' tree.
>
> Currently you are the only contact for problems - let me know if I
> should add someone else (or a list).
Also cc the scsi mailing list for merge problems, just in case.
Thanks,
James
next prev parent reply other threads:[~2014-05-21 2:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 14:06 [ANNOUNCE] scsi patch queue tree Christoph Hellwig
2014-05-20 0:03 ` Stephen Rothwell
2014-05-20 5:39 ` Christoph Hellwig
2014-05-20 23:46 ` Stephen Rothwell
2014-05-21 2:25 ` James Bottomley [this message]
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=1400639101.2481.19.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--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 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.