From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jim Davis <jim.epost@gmail.com>,
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,
linux-media <linux-media@vger.kernel.org>
Subject: Re: randconfig build errors with next-20130620, in several drivers/media
Date: Sat, 22 Jun 2013 16:26:36 +0200 [thread overview]
Message-ID: <2349088.sJtDCiEhsm@avalon> (raw)
In-Reply-To: <51C50101.1000300@infradead.org>
Hi Randy,
On Friday 21 June 2013 18:42:25 Randy Dunlap wrote:
> On 06/21/13 17:27, Laurent Pinchart wrote:
> > On Thursday 20 June 2013 11:52:44 Jim Davis wrote:
> >> Building with the attached random configuration file generates errors in
> >> both
> >
> > [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.
>
> Yes, same for me: USB_VIDEO_CLASS=m instead of =y.
>
> However, please check the attached config file (as reported on June 17).
>
> On linux-next of 20130621 it still produces:
>
> CONFIG_USB_VIDEO_CLASS=y
> CONFIG_VIDEO_V4L2=m
> CONFIG_USB=m
I've just sent a patch to linux-media (you've been CC'ed) to fix this.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-06-22 14:26 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
2013-06-22 1:42 ` Randy Dunlap
2013-06-22 14:26 ` Laurent Pinchart [this message]
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=2349088.sJtDCiEhsm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jim.epost@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.com \
--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.