[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTilXXNQAcU9os4UuG6WMgvVuSYYPglWzaRhO6Xwx@mail.gmail.com>
Date: Fri, 4 Jun 2010 06:39:40 -0600
From: Grant Likely <grant.likely@...retlab.ca>
To: Paul Mackerras <paulus@...ba.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Russell King <rmk@....linux.org.uk>,
Daniel Walker <dwalker@...eaurora.org>,
Kevin Hilman <khilman@...prootsystems.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-msm@...r.kernel.org,
Catalin Marinas <Catalin.Marinas@....com>
Subject: Re: ARM defconfig files
On Thu, Jun 3, 2010 at 6:36 PM, Paul Mackerras <paulus@...ba.org> wrote:
> On Thu, Jun 03, 2010 at 01:31:07PM -0700, Linus Torvalds wrote:
>
>> Now, the above is a _trivial_ one. And it's actually broken, because I
>> should not have forced CONFIG_USB (it depends on CONFIG_USB_SUPPORT).
>
> Seems to me that the brokenness of select is the main technical issue
> stopping us getting rid of the defconfigs. If there was a way to tell
> the Kconfig machinery "I want CONFIG_USB on, you figure out what has
> to be enabled for that to make sense" then it would all work. But
> that's a hard problem (and may possibly have multiple solutions).
Yes, I think you're right. If select was 'smart', then the whole
issue kind of goes away. But as you say, that is a hard problem.
In the mean time, I'd be satisfied with a solution that punted out an
error at configure time if select requirements did not get met. I
should look at the patch Catalin posted.
g.
--
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/
Powered by blists - more mailing lists