From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: [BUILD FAILURE 11/12] Next April 21 : PPC64 randconfig [drivers/usb/host/ohci-hcd.o] Date: Tue, 21 Apr 2009 20:00:37 -0700 Message-ID: <49EE8855.1080306@oracle.com> References: <1240340081.9110.144.camel@subratamodak.linux.ibm.com> <5A202317-5104-4784-845B-B8C46E0A3C48@kernel.crashing.org> <49EE4341.50701@oracle.com> <200904211919.38104.david-b@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200904211919.38104.david-b@pacbell.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@ozlabs.org Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@ozlabs.org To: David Brownell Cc: sachinp , Stephen Rothwell , samr , linux-usb@vger.kernel.org, linux-kernel , Linuxppc-dev , linux-next , subrata@linux.vnet.ibm.com, Alexander Beregalov List-Id: linux-next.vger.kernel.org David Brownell wrote: > On Tuesday 21 April 2009, Randy Dunlap wrote: >>> Since its feasible to say 'n' to both we get the compile error. How do >>> we enforce having at least one set? >> Looks like using "choice" without "optional" would do it. >> See Documentation/kbuild/kconfig-language.txt and various examples >> in Kconfig* files. > > That won't quite work ... "at least one" includes "two" > (i.e. a PCI card in little-endian, a native controller > in big-endian). Real-world systems need such configs, > or so I'm told, and that's why their supported. Yes, I see. > Is there maybe a way to force Kconfig to just reject > such illegal configs -- neither option set -- rather > than trying some how to fix it? Not that I know of. cc-ing Sam. > Or maybe ... if neither one is set, have the header > force both on, and issue a warning. That should be doable. We'd prefer to catch it via Kconfig, but that doesn't look promising just now. -- ~Randy