mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: David Miller <davem@davemloft.net>
Cc: mst@redhat.com, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org, sfr@canb.auug.org.au, hjk@hansjkoch.de,
	gregkh@linuxfoundation.org, stephen@networkplumber.org,
	sean.hefty@intel.com, fx.lebail@yahoo.com, jasowang@redhat.com,
	hannes@stressinduktion.org, wuzhy@linux.vnet.ibm.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH] iovec: move memcpy_from/toiovecend to lib/iovec.c
Date: Fri, 20 Jun 2014 11:11:38 -0700	[thread overview]
Message-ID: <1403287898.30764.17.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <20140619.210637.1702701955085552032.davem@davemloft.net>

On Thu, 2014-06-19 at 21:06 -0700, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Thu, 19 Jun 2014 21:22:56 +0300
> 
> > ERROR: "memcpy_fromiovecend" [drivers/vhost/vhost_scsi.ko] undefined!
> > 
> > commit 9f977ef7b671f6169eca78bf40f230fe84b7c7e5
> >     vhost-scsi: Include prot_bytes into expected data transfer length
> > in target-pending makes drivers/vhost/scsi.c call memcpy_fromiovecend().
> > This function is not available when CONFIG_NET is not enabled.
> > 
> > socket.h already includes uio.h, so no callers need updating.
> > 
> > Reported-by: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > 
> > David, could you please ack merging this through
> > target-pending to avoid dependency issues?
> 
> Yep, this looks fine:
> 
> Signed-off-by: David S. Miller <davem@davemloft.net>

Applied to target-pending/queue, and will include in the next PULL
request.

Thanks folks.

--nab


      reply	other threads:[~2014-06-20 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 18:22 Michael S. Tsirkin
2014-06-19 19:12 ` Randy Dunlap
2014-06-20  4:06 ` David Miller
2014-06-20 18:11   ` Nicholas A. Bellinger [this message]

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=1403287898.30764.17.camel@haakon3.risingtidesystems.com \
    --to=nab@linux-iscsi.org \
    --cc=davem@davemloft.net \
    --cc=fx.lebail@yahoo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hannes@stressinduktion.org \
    --cc=hjk@hansjkoch.de \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sean.hefty@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=stephen@networkplumber.org \
    --cc=wuzhy@linux.vnet.ibm.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
all inboxes | Powered by JetHome®