[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <506A2439.2050408@xenotime.net>
Date:	Mon, 01 Oct 2012 16:16:09 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Ohad Ben-Cohen <ohad@...ery.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Sept 24 (remoteproc)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
