All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org, Asias He <asias@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] vhost-scsi: Depend on NET for memcpy_fromiovec
Date: Wed, 15 May 2013 14:47:53 +0930	[thread overview]
Message-ID: <8761yk254u.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1368579583-13097-1-git-send-email-asias@redhat.com>

Asias He <asias@redhat.com> writes:
> scsi.c includes vhost.c which uses memcpy_fromiovec.
>
> This patch fixes this build failure.
>
>    From Randy Dunlap:
>    '''
>    on x86_64:
>
>    ERROR: "memcpy_fromiovec" [drivers/vhost/vhost_scsi.ko] undefined!
>
>    It needs to depend on NET since net/core/ provides that function.
>    '''

Proper fix please.

Though I can't see why you thought this was a good idea.  Nonetheless, I
shan't highlight why: I have far too much respect for your intellects
and abilities.

No, don't thank me!
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Asias He <asias@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org, Asias He <asias@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH] vhost-scsi: Depend on NET for memcpy_fromiovec
Date: Wed, 15 May 2013 14:47:53 +0930	[thread overview]
Message-ID: <8761yk254u.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1368579583-13097-1-git-send-email-asias@redhat.com>

Asias He <asias@redhat.com> writes:
> scsi.c includes vhost.c which uses memcpy_fromiovec.
>
> This patch fixes this build failure.
>
>    From Randy Dunlap:
>    '''
>    on x86_64:
>
>    ERROR: "memcpy_fromiovec" [drivers/vhost/vhost_scsi.ko] undefined!
>
>    It needs to depend on NET since net/core/ provides that function.
>    '''

Proper fix please.

Though I can't see why you thought this was a good idea.  Nonetheless, I
shan't highlight why: I have far too much respect for your intellects
and abilities.

No, don't thank me!
Rusty.

  parent reply	other threads:[~2013-05-15  5:20 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  4:17 linux-next: Tree for May 14 Stephen Rothwell
2013-05-14  4:17 ` Stephen Rothwell
2013-05-14 19:16 ` linux-next: Tree for May 14 (vhost_scsi) Randy Dunlap
2013-05-14 19:16 ` Randy Dunlap
2013-05-14 23:55   ` Stephen Rothwell
2013-05-14 23:55   ` Stephen Rothwell
2013-05-15  0:59     ` [PATCH] vhost-scsi: Depend on NET for memcpy_fromiovec Asias He
2013-05-15  0:59       ` Asias He
2013-05-15  3:10       ` Nicholas A. Bellinger
2013-05-15  3:44         ` Asias He
2013-05-15  3:44           ` Asias He
2013-05-15  3:10       ` Nicholas A. Bellinger
2013-05-15  5:17       ` Rusty Russell
2013-05-15  5:17       ` Rusty Russell [this message]
2013-05-15  5:17         ` Rusty Russell
2013-05-15 22:37         ` Nicholas A. Bellinger
2013-05-15 22:37           ` Nicholas A. Bellinger
2013-05-15 23:35           ` Rusty Russell
2013-05-15 23:35             ` Rusty Russell
2013-05-16  2:16             ` Asias He
2013-05-16  2:16               ` Asias He
2013-05-16  3:10             ` David Miller
2013-05-16  3:10               ` David Miller
2013-05-16  6:46               ` Michael S. Tsirkin
2013-05-16  6:46                 ` Michael S. Tsirkin
2013-05-16  9:10                 ` David Miller
2013-05-16  9:10                   ` David Miller
2013-05-16  1:48           ` Asias He
2013-05-16  1:48             ` Asias He
2013-05-16  6:42           ` Michael S. Tsirkin
2013-05-16  6:42             ` Michael S. Tsirkin
2013-05-16  2:08         ` Asias He
2013-05-16  2:08           ` Asias He
2013-05-16  3:34           ` Rusty Russell
2013-05-16  3:55             ` Joe Perches
2013-05-16  3:55             ` Joe Perches
2013-05-16 23:42               ` Rusty Russell
2013-05-16 23:42                 ` Rusty Russell
2013-05-17  4:42                 ` Randy Dunlap
2013-05-17  4:42                 ` Randy Dunlap
2013-05-17  6:55                   ` Rusty Russell
2013-05-20  2:07                     ` Asias He
2013-05-20 16:43                       ` Dmitry Torokhov
2013-05-23  7:30                 ` Michael S. Tsirkin
2013-05-23  7:30                   ` Michael S. Tsirkin
2013-05-16  4:35             ` Asias He
2013-05-16  4:35               ` Asias He
2013-05-16  6:36             ` Michael S. Tsirkin
2013-05-16  6:36               ` Michael S. Tsirkin
2013-05-16  3:34           ` Rusty Russell

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=8761yk254u.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=target-devel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.