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?
I think you're free to do so because .config defines are not API anyway
and anyone who thinks so should get off the bad sh*t he's smoking.
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
