From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Brownell <david-b@pacbell.net>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>, samr <sam@ravnborg.org>,
linux-usb@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
linux-next <linux-next@vger.kernel.org>,
subrata@linux.vnet.ibm.com,
Alexander Beregalov <a.beregalov@gmail.com>
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 [thread overview]
Message-ID: <49EE8855.1080306@oracle.com> (raw)
In-Reply-To: <200904211919.38104.david-b@pacbell.net>
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
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Brownell <david-b@pacbell.net>
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>,
samr <sam@ravnborg.org>
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 [thread overview]
Message-ID: <49EE8855.1080306@oracle.com> (raw)
In-Reply-To: <200904211919.38104.david-b@pacbell.net>
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
next prev parent reply other threads:[~2009-04-22 3:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 18:54 [BUILD FAILURE 11/12] Next April 21 : PPC64 randconfig [drivers/usb/host/ohci-hcd.o] Subrata Modak
2009-04-21 18:54 ` Subrata Modak
2009-04-21 18:54 ` Subrata Modak
[not found] ` <1240340081.9110.144.camel-NRFfyExJdYpgXGGE5LP+UZlqa2bBAFbm0E9HWUfgJXw@public.gmane.org>
2009-04-21 19:03 ` David Brownell
2009-04-21 19:03 ` David Brownell
2009-04-21 19:03 ` David Brownell
2009-04-21 21:37 ` Kumar Gala
2009-04-21 21:37 ` Kumar Gala
2009-04-21 22:05 ` Randy Dunlap
2009-04-21 22:05 ` Randy Dunlap
[not found] ` <49EE4341.50701-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-04-22 2:19 ` David Brownell
2009-04-22 2:19 ` David Brownell
2009-04-22 2:19 ` David Brownell
2009-04-22 3:00 ` Randy Dunlap [this message]
2009-04-22 3:00 ` Randy Dunlap
[not found] ` <49EE8855.1080306-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-04-22 7:30 ` Arnd Bergmann
2009-04-22 7:30 ` Arnd Bergmann
2009-04-22 7:30 ` Arnd Bergmann
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=49EE8855.1080306@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=a.beregalov@gmail.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.com \
/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.