[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5790855.fto4zA3B21@avalon>
Date: Sat, 22 Jun 2013 02:27:20 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Jim Davis <jim.epost@...il.com>
Cc: sfr@...b.auug.org.au, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, pawel@...iak.com,
m.szyprowski@...sung.com, kyungmin.park@...sung.com
Subject: Re: randconfig build errors with next-20130620, in several drivers/media
Hi,
On Thursday 20 June 2013 11:52:44 Jim Davis wrote:
> Building with the attached random configuration file generates errors in
> both
>
> drivers/media/v4l2-core
> drivers/media/usb/uvc
>
> LD init/built-in.o
> /home/jim/linux-next/linux/drivers/media/v4l2-core/videobuf2-core.c:2577:
> undefi ned reference to `video_devdata'
[snip]
> /home/jim/linux-next/linux/drivers/media/v4l2-core/videobuf2-core.c:2591:
> undefi ned reference to `v4l2_fh_release'
[snip]
> /home/jim/linux-next/linux/drivers/media/v4l2-core/videobuf2-core.c:1980:
> undefi ned reference to `v4l2_event_pending'
[snip]
> drivers/built-in.o: In function `uvc_delete':
> /home/jim/linux-next/linux/drivers/media/usb/uvc/uvc_driver.c:1606:
> undefined re ference to `usb_put_intf'
[snip]
The issue seem to be caused by USB_VIDEO_CLASS=y and VIDEO_V4L2=m && USB=m.
I'm not sure what made that combination possible, but I haven't been able to
reproduce it locally on next-20130620. Running make with the attached config
turns USB_VIDEO_CLASS=y into USB_VIDEO_CLASS=m.
--
Regards,
Laurent Pinchart
--
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