[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11778979.HbWgmZUCnF@wuerfel>
Date: Tue, 16 Feb 2016 16:08:34 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Vladimir Murzin <vladimir.murzin@....com>, mark.rutland@....com,
devicetree@...r.kernel.org, linux@....linux.org.uk,
pawel.moll@....com, ijc+devicetree@...lion.org.uk,
gregkh@...uxfoundation.org, daniel.lezcano@...aro.org,
linux-kernel@...r.kernel.org, robh+dt@...nel.org,
andy.shevchenko@...il.com, galak@...eaurora.org,
linux-serial@...r.kernel.org, u.kleine-koenig@...gutronix.de,
tglx@...utronix.de, linux-api@...r.kernel.org, jslaby@...e.cz
Subject: Re: [PATCH v3 08/10] ARM: configs: add MPS2 defconfig
On Tuesday 16 February 2016 14:51:59 Vladimir Murzin wrote:
> >
> > Why CONFIG_EMBEDDED? You probably mean CONFIG_EXPERT, but then what do
> > you need that for?
>
> TBH, I have no special requirement for this option to be set and now,
> looking at Kconfig entry for this option, I think that I got it here
> because I stated configuration with allnoconfig.
>
> OTOH, I don't see how harmful it can be since description says:
>
> This option should be enabled if compiling the kernel for
> an embedded system so certain expert options are available
> for configuration
>
> yes, it selects CONFIG_EXPERT and that had side effect that, for
> example, CONFIG_NAMESPACE could be compiled out.
>
> Have I missed something around it?
Just the history behind this symbol. We removed it a while ago in
favor if CONFIG_EXPERT, assuming that it makes it clearer that it's
not just for embedded systems, or for systems with small memory.
It's basically a zombie symbol that nobody should use directly
(independent of what the documentation says...).
Arnd
Powered by blists - more mailing lists