DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=WVQkjd3UnsUCxv7Fdt7Ym6bRNB8OaHmzGZf5wB51CG6YDlAAx7Mrzfm/hmZU/hbiRvKEka0zI/5+tISouCS3Cv6pkvuZGQbNcaol4biFopai1Ax42Es1Rmpo/Pgup5t6Iw2X6OcnI9xld5z9Q+VFvoQPyWBVmovVZMmIneqAAJU=  ;
From: David Brownell <david-b@pacbell.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [BUILD FAILURE 11/12] Next April 21 : PPC64 randconfig [drivers/usb/host/ohci-hcd.o]
Date: Tue, 21 Apr 2009 19:19:37 -0700
User-Agent: KMail/1.9.10
Cc: Kumar Gala <galak@kernel.crashing.org>, subrata@linux.vnet.ibm.com,
       linux-usb@vger.kernel.org, "Linuxppc-dev" <Linuxppc-dev@ozlabs.org>,
       Stephen Rothwell <sfr@canb.auug.org.au>,
       "linux-next" <linux-next@vger.kernel.org>,
       sachinp <sachinp@linux.vnet.ibm.com>,
       "linux-kernel" <linux-kernel@vger.kernel.org>,
       Alexander Beregalov <a.beregalov@gmail.com>
References: <1240340081.9110.144.camel@subratamodak.linux.ibm.com> <5A202317-5104-4784-845B-B8C46E0A3C48@kernel.crashing.org> <49EE4341.50701@oracle.com>
In-Reply-To: <49EE4341.50701@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200904211919.38104.david-b@pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1008
Lines: 27

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.

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?

Or maybe ... if neither one is set, have the header
force both on, and issue a warning.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/