From: "Michael S. Tsirkin" <mst@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
nab@linux-iscsi.org
Subject: Re: linux-next: Tree for Jun 19 (vhost_scsi)
Date: Thu, 19 Jun 2014 21:22:19 +0300 [thread overview]
Message-ID: <20140619182219.GA22644@redhat.com> (raw)
In-Reply-To: <53A31ACF.5020302@infradead.org>
On Thu, Jun 19, 2014 at 10:15:59AM -0700, Randy Dunlap wrote:
> On 06/18/14 23:16, Stephen Rothwell wrote:
> > Hi all,
> >
> > The powerpc allyesconfig is again broken more than usual.
> >
> > Changes since 20140618:
> >
>
> on x86_64:
> CONFIG_NET is not enabled.
>
> ERROR: "memcpy_fromiovecend" [drivers/vhost/vhost_scsi.ko] undefined!
>
> drivers/vhost/scsi.c calls memcpy_fromiovecend().
> This function is not available when CONFIG_NET is not enabled.
Yes, that's nab's tree using memcpy_fromiovecend.
I'll send a patch to fix that.
>
> --
> ~Randy
next prev parent reply other threads:[~2014-06-19 18:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 6:16 linux-next: Tree for Jun 19 Stephen Rothwell
2014-06-19 17:15 ` linux-next: Tree for Jun 19 (vhost_scsi) Randy Dunlap
2014-06-19 18:22 ` Michael S. Tsirkin [this message]
2014-06-19 17:24 ` linux-next: Tree for Jun 19 (drm/i915) Randy Dunlap
2014-06-24 11:43 ` Jani Nikula
2014-06-24 11:43 ` Jani Nikula
2014-06-24 23:01 ` Rafael J. Wysocki
2014-07-07 14:54 ` Daniel Vetter
2014-07-07 20:01 ` Rafael J. Wysocki
2014-07-07 20:01 ` Rafael J. Wysocki
2014-07-07 20:06 ` Daniel Vetter
2014-07-07 20:06 ` Daniel Vetter
2014-07-07 21:49 ` Rafael J. Wysocki
2014-07-07 21:49 ` Rafael J. Wysocki
2014-07-07 23:58 ` Rafael J. Wysocki
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=20140619182219.GA22644@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.