linux-kernel - Re: [PATCH] printk: Use symbolic defines for console loglevels instead of numbers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 17 Mar 2015 16:59:29 +0600
From:	Alexander Kuleshov <kuleshovmail@...il.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Tony Lindgren <tony@...mide.com>,
	Russell King <linux@....linux.org.uk>,
	Paul Mackerras <paulus@...ba.org>,
	Michael Ellerman <mpe@...erman.id.au>,
	Gavin Shan <gwshan@...ux.vnet.ibm.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] printk: Use symbolic defines for console loglevels
 instead of numbers

2015-03-16 21:09 GMT+06:00 Joe Perches <joe@...ches.com>:
> On Mon, 2015-03-16 at 15:01 +0600, Alexander Kuleshov wrote:
>> Signed-off-by: Alexander Kuleshov <kuleshovmail@...il.com>
>
> Perhaps the entries for #define CONSOLE_LOGLEVEL_<FOO>
> from printk.h and #define LOGLEVEL_<FOO> from kern_levels.h
> can be consolidated and rationalized as well.
>
>

Hello Joe,

yes good idea. What was the purpose of adding LOGLEVEL_<FOO> macro? I see
that CONSOLE_LOGLEVEL_<FOO> were added earlier. what if we remove LOGLEVL_<FOO>
macro and add/adapt missing as CONSOLE_LOGLEVEL_<FOO>, like
CONSOLE_LOGLEVEL_SCHED and etc...?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/