[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1906719446.2930546.1361398782879.JavaMail.root@vmware.com>
Date: Wed, 20 Feb 2013 14:19:42 -0800 (PST)
From: Andy King <acking@...are.com>
To: Paul Moore <pmoore@...hat.com>
Cc: netdev@...r.kernel.org
Subject: Re: Problems with VSOCK?
Hi Paul,
> I'm currently looking at the VSOCK implementation in netdev-next to determine
> what we need in the way of LSM hooks and I ran into a few things which look
> rather odd:
>
> * net/vmw_sock/Kconfig
>
> VMWARE_VMCI_SOCKETS depends on VMWARE_VMCI which doesn't look to be defined
> anywhere, help? For what it is worth, removing the VMWARE_VMCI dependency
Ah, I think this is the same problem someone else had a few days ago. VMCI
came in via Greg's char-misc-next tree, and it hasn't merged into Dave's
tree yet. But the top-level linux-next tree now has all required modules:
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
Sorry about them coming in from different trees :/
Thanks!
- Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists