From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, Andy King <acking@vmware.com>,
Dmitry Torokhov <dtor@vmware.com>
Subject: Re: [PATCH] misc/vmw_vmci: VMWARE_VMCI depends on NET
Date: Mon, 1 Apr 2013 12:29:39 -0700 [thread overview]
Message-ID: <20130401192939.GA31983@kroah.com> (raw)
In-Reply-To: <1364791439-28396-1-git-send-email-linux@roeck-us.net>
On Sun, Mar 31, 2013 at 09:43:59PM -0700, Guenter Roeck wrote:
> Fix:
>
> ERROR: "memcpy_toiovec" [drivers/misc/vmw_vmci/vmw_vmci.ko] undefined!
> ERROR: "memcpy_fromiovec" [drivers/misc/vmw_vmci/vmw_vmci.ko] undefined!
>
> Both functions are defined in the core networking code.
This is already in linux-next, thanks.
greg k-h
next prev parent reply other threads:[~2013-04-01 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 4:43 [PATCH] misc/vmw_vmci: VMWARE_VMCI depends on NET Guenter Roeck
2013-04-01 16:11 ` Randy Dunlap
2013-04-01 19:29 ` Greg Kroah-Hartman [this message]
2013-04-01 20:02 ` Guenter Roeck
2013-04-01 20:11 ` Greg Kroah-Hartman
2013-04-01 22:17 ` Guenter Roeck
2013-04-01 21:53 ` Randy Dunlap
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=20130401192939.GA31983@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acking@vmware.com \
--cc=dtor@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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