From: Borislav Petkov <bp@alien8.de>
To: Alex Elder <alex.elder@linaro.org>
Cc: Alex Elder <elder@linaro.org>,
akpm@linux-foundation.org, ak@linux.intel.com, bp@suse.de,
jack@suse.cz, john.stultz@linaro.org, pmladek@suse.cz,
rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] printk: rename DEFAULT_MESSAGE_LOGLEVEL
Date: Wed, 9 Jul 2014 17:13:51 +0200 [thread overview]
Message-ID: <20140709151351.GD5254@pd.tnic> (raw)
In-Reply-To: <53BD5B64.3010703@linaro.org>
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.
--
next prev parent reply other threads:[~2014-07-09 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:04 [PATCH 0/4] printk: some minor fixups Alex Elder
2014-07-09 13:04 ` [PATCH 1/4] printk: rename DEFAULT_MESSAGE_LOGLEVEL Alex Elder
2014-07-09 15:00 ` Borislav Petkov
2014-07-09 15:10 ` Alex Elder
2014-07-09 15:13 ` Borislav Petkov [this message]
2014-07-09 15:14 ` Alex Elder
2014-07-09 15:17 ` Borislav Petkov
2014-07-09 13:04 ` [PATCH 2/4] printk: fix some comments Alex Elder
2014-07-09 15:53 ` Petr Mládek
2014-07-09 13:04 ` [PATCH 3/4] printk: use a clever macro Alex Elder
2014-07-09 15:05 ` Borislav Petkov
2014-07-09 16:19 ` Petr Mládek
2014-07-09 16:24 ` Borislav Petkov
2014-07-09 16:32 ` Petr Mládek
2014-07-09 16:40 ` Borislav Petkov
2014-07-09 17:58 ` Geert Uytterhoeven
2014-07-09 18:15 ` Alex Elder
2014-07-09 13:04 ` [PATCH 4/4] printk: miscellaneous cleanups Alex Elder
2014-07-09 16:29 ` Petr Mládek
2014-07-09 16:45 ` Alex Elder
2014-07-09 16:03 ` Alex Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140709151351.GD5254@pd.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex.elder@linaro.org \
--cc=bp@suse.de \
--cc=elder@linaro.org \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.