From: James Bottomley <James.Bottomley@HansenPartnership•com>
To: "Michael S. Tsirkin" <mst@redhat•com>
Cc: linux-next@vger•kernel.org, sfr@canb•auug.org.au,
linux-pci@vger•kernel.org, netdev@vger•kernel.org,
linux-scsi@vger•kernel.org
Subject: Re: (repost) vhost tree for linux-next
Date: Sun, 27 Nov 2011 08:00:08 -0600 [thread overview]
Message-ID: <1322402408.2992.4.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20111127135916.GB23302@redhat.com>
On Sun, 2011-11-27 at 15:59 +0200, Michael S. Tsirkin wrote:
> On Sun, Nov 27, 2011 at 07:38:59AM -0600, James Bottomley wrote:
> > On Sun, 2011-11-27 at 14:48 +0200, Michael S. Tsirkin wrote:
> > > I normally merge things through Dave, Rusty, Jesse or Jens,
> > > not directly to Linus. However, sometimes there's a large change
> > > (for example, my recent RFC for pci_iomap changes)
> > > where estimating how it interacts with other platforms and planned
> > > changes in the next kernel would be beneficial.
> > >
> > > For this purpose, it would be helpful if my tree were added to linux-next.
> > > The tree is:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> > >
> > > Could you do this please?
> > > (The current contents of that tree was posted for review/feedback
> > > for the first time today. It might make sense to give it a few days
> > > for any responses ...)
> >
> > I'm a little confused by your to: field. This is a linux-arch issue,
> > isn't it, since it's altering architecture implementations of a PCI
> > function rather than altering anything in SCSI or net?
> >
> > James
>
> Yes. Stephen Rothwell asked me to Cc widely to see if anyone
> objects to picking this stuff in linux-next.
> Sorry about any confusion.
I;m fine with that, but the fact that you didn't send it to linux-arch
was more my point ...
James
next prev parent reply other threads:[~2011-11-27 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 20:38 vhost tree for linux-next Michael S. Tsirkin
2011-11-24 23:42 ` Stephen Rothwell
2011-11-27 12:48 ` (repost) " Michael S. Tsirkin
2011-11-27 13:38 ` James Bottomley
2011-11-27 13:59 ` Michael S. Tsirkin
2011-11-27 14:00 ` James Bottomley [this message]
2011-11-28 23:36 ` Stephen Rothwell
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=1322402408.2992.4.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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