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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
