From: Andy King <acking@vmware.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Dmitry Torokhov <dtor@vmware.com>,
George Zhang <georgezhang@vmware.com>
Subject: Re: failure when attempting to build vmci_transport on net-next
Date: Thu, 14 Feb 2013 06:54:41 -0800 (PST) [thread overview]
Message-ID: <1074156873.1496876.1360853681687.JavaMail.root@vmware.com> (raw)
In-Reply-To: <511CB353.3000704@mellanox.com>
Hi Or,
> I didn't manage to get the VMWARE_VMCI_VSOCKETS directive to be set,
> unless I added the below patch, and
> once that done got the tons of errors below, am I doing something wrong?
That's because VMCI, which is necessary for the vSock vmci_transport,
came in via Greg's char-misc-next tree, and it hasn't yet merged all the
way over to Dave's net-next tree.
However, I just checked the top-level linux-next tree and it has both,
so perhaps you could try that instead?
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
Thanks!
- Andy
next prev parent reply other threads:[~2013-02-14 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 9:50 failure when attempting to build vmci_transport on net-next Or Gerlitz
2013-02-14 14:54 ` Andy King [this message]
2013-02-14 15:06 ` Or Gerlitz
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=1074156873.1496876.1360853681687.JavaMail.root@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=dtor@vmware.com \
--cc=georgezhang@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
/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