linux-kernel - Re: [RFC] New kernel-message logging API

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 24 Sep 2007 23:54:14 -0700
From:	Joe Perches <joe@...ches.com>
To:	linux@...izon.com
Cc:	vegard.nossum@...izon.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC] New kernel-message logging API

On Tue, 2007-09-25 at 00:58 -0400, linux@...izon.com wrote:
> Even the "kp_" prefix is actually pretty unnecessary.  It's "info"
> and a human-readable string that make it recognizable as a log message.

While I agree a prefix isn't necessary, info, warn, err
are already frequently #define'd and used.

kp_<level> isn't currently in use.

$ egrep -r -l --include=*.[ch] "^[[:space:]]*#[[:space:]]*define[[:space:]]+(info|err|warn)\b" * | wc -l
29


-
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/