Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED

[Andrew Jones]

On Tue, Jan 17, 2012 at 12:54:01PM -0800, David Rientjes wrote:
> When it's configurable only for CONFIG_EMBEDDED, then you can propose that 
> to the HID maintainers.  If they agree, then we don't care if users 
> currently with CONFIG_EXPERT=y and CONFIG_EMBEDDED=n lose the option, but 
> that needs to be handled on a case-by-case basis when breaking backwards 
> compatibility.
> 

Ah, I think I may have just gotten to the bottom of this long, useless
thread. Based on your last email and by rereading what you wrote above.
You seem to believe a patch like

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 82928f5..ec1023d 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -771,7 +771,7 @@ config DEBUG_WRITECOUNT

 config DEBUG_MEMORY_INIT
        bool "Debug memory initialisation" if EXPERT
-       default !EXPERT
+       default !EMBEDDED
        help
          Enable this for additional checks during memory initialisation.
          The sanity checks verify aspects of the VM such as the memory
model

means that configs with CONFIG_EXPERT=y and CONFIG_EMBEDDED=n would then
generate kernels that no longer have the additional memory checks. Those
checks are generally a good thing, and in fact the config help for that
option says "If unsure, say Y". So a general kernel, using the general
kernel option, EXPERT, but not the specific option, EMBEDDED, would be
upset when losing that option.

Your problem is that your logic is backwards. The kernel right now has
precisely that issue, due to 6a108a14fa35. If EXPERT is on, then you'll
lose DEBUG_MEMORY_INIT. That, and all the other silently changed defaults,
is exactly what this patch fixes.

Please review the logic and the entire patch again.
--
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/