Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED

[Andrew Morton]

On Wed, 18 Jan 2012 06:08:30 -0500 (EST)
Andrew Jones <drjones@xxxxxxxxxx> wrote:

> CONFIG_EMBEDDED to CONFIG_EXPERT

I don't think either of these things have been successful.  At least, I
haven't seen any evidence of it.

My take on these is that EMBEDDED is a handy way for embedded kernel
developers to start out with a config which is more appropriate to an
embedded device kernel.  Of course, the resulting config will be very
different from what they eventually use in their product and I expect
that the head-start which EMBEDDED gave was of negligible benefit.

The development lifetime for an embedded product kernel is months, more
likely years.  The team will invest the time to carefully select and
maintain their kernel configuration.

IOW, I expect that EMBEDDED is useless and we may as well do away with it.


And ditto EXPERT.  Is there really any benefit in hiding config options
from developers so they won't burn their fingers?  Or is there some
other reason for EXPERT?

Anyway, we already have a way to prevent fingers from getting burnt:
defconfig.  Start out with that and carefully modify it.


I can see an argument for retaining EXPERIMENTAL: as a way of telling
people that the particular feature might not yet be ready for prime
time.  But I suggest that we tip both CONFIG_EXPERT and CONFIG_EMBEDDED
into the ole bit bucket.  What do you guys think would be the negative
consequences of doing this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/