[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1201121255310.17287@chino.kir.corp.google.com>
Date: Thu, 12 Jan 2012 12:59:04 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Arnd Bergmann <arnd@...db.de>
cc: Andrew Jones <drjones@...hat.com>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, mingo@...e.hu,
david.woodhouse@...el.com, gregkh@...e.de, davem@...emloft.net,
axboe@...nel.dk, holt@....com, linux-arch@...r.kernel.org,
linux@....linux.org.uk, hskinnemoen@...il.com,
egtvedt@...fundet.no, msalter@...hat.com, a-jacquiot@...com,
starvik@...s.com, jesper.nilsson@...s.com, dhowells@...hat.com,
takata@...ux-m32r.org, geert@...ux-m68k.org,
yasutake.koichi@...panasonic.com, jonas@...thpole.se,
kyle@...artin.ca, deller@....de, jejb@...isc-linux.org,
chris@...kel.net, greg@...ah.com, davej@...hat.com,
airlied@...ux.ie, jkosina@...e.cz, mchehab@...radead.org,
johannes@...solutions.net, linville@...driver.com
Subject: Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED
On Thu, 12 Jan 2012, Arnd Bergmann wrote:
> > I would think that something like CONFIG_SMALLMEM would identify those
> > candidates (for things like SLOB) and then you could separate the rest
> > based on the platform they exist for since you're essentially introducing
> > a new config symbol here that existed in the past but are now using it
> > with different semantics.
>
> The CONFIG_SMALLMEM would also require people to know what they are doing,
> beyond what we expect the average person building a kernel to, which is
> just what CONFIG_EXPERT means, and the same reason why we ended up renaming
> CONFIG_EMBEDDED to CONFIG_EXPERT. People have a very different understanding
> of what "embedded" actually means, and not all of those require small
> memory footprint or even a custom kernel. Let's just stay with CONFIG_EXPERT.
>
I think the intention here, correct me if I'm wrong, is to aid those who
are configuring the kernel to prefer certain options over others for
special devices such as embedded devices that require a low memory
footprint. So if a CONFIG_SMALLMEM were to exist with helpful text
associated with it, then it could be chosen to enable things like
CONFIG_SLOB that the user may not previously have looked for or understood
and wouldn't make sense without CONFIG_SMALLMEM unless debugging.
--
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