[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101014183448.GA3187@elte.hu>
Date: Thu, 14 Oct 2010 20:34:48 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Casey Dahlin <cdahlin@...hat.com>, x86@...nel.org,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [patch] x86: allow ZONE_DMA to be configurable
* H. Peter Anvin <hpa@...or.com> wrote:
> On 10/14/2010 09:00 AM, Pekka Enberg wrote:
>
> >> CONFIG_EMBEDDED *is* "I am a user who (think I) know what I'm
> >> doing". That is *what it is* and *all it is*.
> >
> > Yup. The naming is quite unfortunate, though. Can we change it to
> > something else?
>
> Funny, this seems to come up repeatedly ;)
I'd suggest to rename CONFIG_EMBEDDED=y to CONFIG_EXPERT=y, but i'd also
suggest to rename all sub-config-options that depend on CONFIG_EXPERT to
have a CONFIG_EXPERT_ prefix.
So we'd have:
CONFIG_EXPERT_CPU_SUP_INTEL=y
CONFIG_EXPERT_MMAP_ALLOW_UNINITIALIZED=y
etc.
That way all the enabled 'expert options' become easily visible in the
.config file and they advertise themselves properly - it's also easily
greppable. In the source code it also becomes self-documenting, it's
obvious when a dependency is 'rare' or 'special' - it has a
CONFIG_EXPERT_ prefix.
Something for the KS i guess.
Thanks,
Ingo
--
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