From: Randy Dunlap <rdunlap@xenotime.net>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sept 24 (remoteproc)
Date: Mon, 01 Oct 2012 16:16:09 -0700 [thread overview]
Message-ID: <506A2439.2050408@xenotime.net> (raw)
In-Reply-To: <5060DA6B.3030806@xenotime.net>
On 09/24/2012 03:10 PM, Randy Dunlap wrote:
> On 09/24/2012 07:53 AM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Today was a train wreck, with lots of new conflicts across several trees
>> and a few build failures as well.
>>
>> Changes since 201209021:
>>
>
This build still fails on linux-next of 20121001 when
VIRTIO is not enabled.
>
> on x86_64:
>
> drivers/built-in.o: In function `rproc_virtio_finalize_features':
> remoteproc_virtio.c:(.text+0x2f9a02): undefined reference to `vring_transport_features'
> drivers/built-in.o: In function `rproc_virtio_del_vqs':
> remoteproc_virtio.c:(.text+0x2f9a74): undefined reference to `vring_del_virtqueue'
> drivers/built-in.o: In function `rproc_virtio_find_vqs':
> remoteproc_virtio.c:(.text+0x2f9c44): undefined reference to `vring_new_virtqueue'
> drivers/built-in.o: In function `rproc_add_virtio_dev':
> (.text+0x2f9e2c): undefined reference to `register_virtio_device'
> drivers/built-in.o: In function `rproc_vq_interrupt':
> (.text+0x2f9db7): undefined reference to `vring_interrupt'
> drivers/built-in.o: In function `rproc_remove_virtio_dev':
> (.text+0x2f9e9f): undefined reference to `unregister_virtio_device'
>
>
> Full randconfig file is attached.
>
>
>
--
~Randy
next prev parent reply other threads:[~2012-10-01 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 14:53 linux-next: Tree for Sept 24 Stephen Rothwell
2012-09-24 15:39 ` linux-next: Tree for Sept 24 (irqchip) Randy Dunlap
2012-09-24 16:07 ` Stephen Rothwell
2012-09-24 16:42 ` Stephen Warren
2012-09-24 16:46 ` Olof Johansson
2012-11-03 1:47 ` Randy Dunlap
2012-09-24 19:50 ` linux-next: Tree for Sept 24 (net/ipv4) Randy Dunlap
2012-09-24 22:02 ` linux-next: Tree for Sept 24 (iommu) Randy Dunlap
2012-09-25 3:23 ` Alex Williamson
2012-09-25 10:16 ` Roedel, Joerg
2012-09-24 22:10 ` linux-next: Tree for Sept 24 (remoteproc) Randy Dunlap
2012-09-30 8:33 ` Ohad Ben-Cohen
2012-10-01 23:16 ` Randy Dunlap [this message]
2012-10-02 8:04 ` Ohad Ben-Cohen
2012-09-24 22:25 ` linux-next: Tree for Sept 24 (net without INET) 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=506A2439.2050408@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ohad@wizery.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).