From: lacombar@gmail.com (Arnaud Lacombe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Remove remaining references of CONFIG_GENERIC_TIME
Date: Mon, 1 Aug 2011 13:20:26 -0400 [thread overview]
Message-ID: <CACqU3MU_oq+RYydenKG_8U08rdJ-N+2hftH+2xEPZU0uVP6i5A@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1108011737030.18706@xanadu.home>
Hi,
On Mon, Aug 1, 2011 at 12:40 PM, Nicolas Pitre <nico@fluxnic.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
next prev parent reply other threads:[~2011-08-01 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 16:14 [PATCH] Remove remaining references of CONFIG_GENERIC_TIME Zoltan Devai
2011-07-30 16:33 ` Sergei Shtylyov
2011-07-30 16:41 ` richard -rw- weinberger
2011-08-01 8:36 ` Russell King - ARM Linux
2011-08-01 10:09 ` Geert Uytterhoeven
2011-08-01 10:14 ` Russell King - ARM Linux
2011-08-01 11:27 ` Geert Uytterhoeven
2011-08-01 14:36 ` Uwe Kleine-König
2011-08-01 15:04 ` Arnaud Lacombe
2011-08-01 15:15 ` Kyle Moffett
2011-08-01 16:08 ` Arnaud Lacombe
2011-08-01 16:40 ` Nicolas Pitre
2011-08-01 17:20 ` Arnaud Lacombe [this message]
2011-08-01 16:48 ` Kyle Moffett
2011-08-01 17:14 ` Arnaud Lacombe
2011-08-01 17:15 ` Arnaud Lacombe
2011-08-01 11:41 ` Zoltan Devai
2011-08-01 14:25 ` Russell King - ARM Linux
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=CACqU3MU_oq+RYydenKG_8U08rdJ-N+2hftH+2xEPZU0uVP6i5A@mail.gmail.com \
--to=lacombar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).