[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACqU3MU_oq+RYydenKG_8U08rdJ-N+2hftH+2xEPZU0uVP6i5A@mail.gmail.com>
Date: Mon, 1 Aug 2011 13:20:26 -0400
From: Arnaud Lacombe <lacombar@...il.com>
To: Nicolas Pitre <nico@...xnic.net>
Cc: Kyle Moffett <kyle@...fetthome.net>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Zoltan Devai <zdevai@...il.com>,
lkml <linux-kernel@...r.kernel.org>, chris@...kel.net,
linux-am33-list@...hat.com, trivial@...nel.org,
user-mode-linux-devel@...ts.sourceforge.net, cmetcalf@...era.com,
linux-arm-kernel@...ts.infradead.org,
linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: [PATCH] Remove remaining references of CONFIG_GENERIC_TIME
Hi,
On Mon, Aug 1, 2011 at 12:40 PM, Nicolas Pitre <nico@...xnic.net> wrote:
> On Mon, 1 Aug 2011, Arnaud Lacombe wrote:
>
>> Moreover, this approach is deemed to fail. The current symbol
>> namespace is tied to an arch, so whenever you do:
>>
>> arch/arm/Kconfig:
>> config FOO
>> bool
>>
>> config BAZ
>> bool
>>
>> drivers/cpufreq/Kconfig
>> config BAR
>> depends on ARM && FOO
>> select BAZ
>>
>> You will end up triggering the warning for every ARCH != ARM...
>
> You can keep a state for those symbols with regard to their level of
> reference. Surely if ARM isn't true, BAZ is not "actively" referenced
> in the end.
>
he :) we enter in compilers optimizations. As much as I agree with
you, that might not be trivial to implement given the internal,
ad-hoc, structure of kconfig. All of that would be useless if we had a
single global namespace.
- Arnaud
--
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