mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Torokhov <dtor@vmware.com>
Cc: pv-drivers@vmware.com, Neil Horman <nhorman@tuxdriver.com>,
	acking@vmware.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davem@davemloft.net
Subject: Re: [Pv-drivers] [PATCH 1/1] VSOCK: Introduce VM Sockets
Date: Fri, 25 Jan 2013 16:22:08 -0800	[thread overview]
Message-ID: <20130126002208.GB5132@kroah.com> (raw)
In-Reply-To: <2312112.Fz0qTjDOJB@dtor-d630.eng.vmware.com>

On Fri, Jan 25, 2013 at 04:15:19PM -0800, Dmitry Torokhov wrote:
> Hi Neil,
> 
> On Friday, January 25, 2013 06:59:53 PM Neil Horman wrote:
> > On Fri, Jan 25, 2013 at 09:37:50AM -0800, acking@vmware.com wrote:
> > > +
> > > +config VMWARE_VSOCK
> > > +	tristate "Virtual Socket protocol"
> > > +	depends on VMWARE_VMCI
> > 
> > What is CONFIG_VMWARE_VMCI?  I don't find that in any Kconfig in the tree?
> > 
> > I''m still looking over the rest, but I get build issues if I just remove
> > the dependency.
> 
> VMCI is in linux-next at the moment.

>From the char-misc-next git tree to be specific.

thanks,

greg k-h

  reply	other threads:[~2013-01-26  0:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 17:37 [PATCH 0/1] VM Sockets for Linux upstreaming acking
2013-01-25 17:37 ` [PATCH 1/1] VSOCK: Introduce VM Sockets acking
2013-01-25 23:59   ` Neil Horman
2013-01-26  0:15     ` [Pv-drivers] " Dmitry Torokhov
2013-01-26  0:22       ` Greg KH [this message]
2013-01-26 18:41       ` Neil Horman
2013-01-28 12:25   ` Gerd Hoffmann
2013-01-31 22:06     ` Andy King
2013-02-01  8:12       ` Gerd Hoffmann
2013-02-04 23:41         ` Andy King
2013-02-07  0:23 [PATCH 0/1] VM Sockets for Linux upstreaming Andy King
2013-02-07  0:23 ` [PATCH 1/1] VSOCK: Introduce VM Sockets Andy King
2013-02-11 14:22   ` Gerd Hoffmann
2013-02-12 15:21     ` Andy King
2013-02-13  3:21       ` [Pv-drivers] " Andy King

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=20130126002208.GB5132@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acking@vmware.com \
    --cc=davem@davemloft.net \
    --cc=dtor@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pv-drivers@vmware.com \
    --cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®