That message should _never_ appear to a user. Anyone who wants to
gratuitously change that can write a suitable help text.
Actually I'm hoping that CML2, if adopted, will allow us to get rid of the
CONFIG_MEMORY_SET cruft in arch/sh/config.in altogether.
But not, of course, until after the initial adoption of the CML2 codebase -
actual changes to the behaviour of the config options _must_ be done
separately to the change in mechanism.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/