linux-kernel - Re: randconfig build errors with next-20130620, in several drivers/media

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2349088.sJtDCiEhsm@avalon>
Date:	Sat, 22 Jun 2013 16:26:36 +0200
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	Jim Davis <jim.epost@...il.com>, 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,
	linux-media <linux-media@...r.kernel.org>
Subject: Re: randconfig build errors with next-20130620, in several drivers/media

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
--
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/