From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, pawel@osciak.com,
m.szyprowski@samsung.com, kyungmin.park@samsung.com
Subject: Re: randconfig build errors with next-20130620, in several drivers/media
Date: Sat, 22 Jun 2013 02:27:20 +0200 [thread overview]
Message-ID: <5790855.fto4zA3B21@avalon> (raw)
In-Reply-To: <20130620185244.GA14176@krebstar.arl.arizona.edu>
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
next prev parent reply other threads:[~2013-06-22 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 18:52 randconfig build errors with next-20130620, in several drivers/media Jim Davis
2013-06-22 0:27 ` Laurent Pinchart [this message]
2013-06-22 1:42 ` Randy Dunlap
2013-06-22 14:26 ` Laurent Pinchart
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=5790855.fto4zA3B21@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jim.epost@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.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 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.