On Wed, Jul 09, 2014 at 10:10:28AM -0500, Alex Elder wrote:
Yes I realized this just sort of moved that sort of problem
to a different place. The change was responding to the
inconsistency in naming in "printk.c". I can control the
effects of that, but I can't predict who might be using
various config options, so I avoided doing that rename.
Was I being overly cautious on the config option name?
I could fix that too and have consistency everywhere.
You mean turn it into CONFIG_MESSAGE_LOGLEVEL_DEFAULT?