linux-kernel - Re: [PATCH v2] checkpatch: support more uppercase $logFunctions

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]

Message-ID: <1426756387.21142.1.camel@perches.com>
Date:	Thu, 19 Mar 2015 02:13:07 -0700
From:	Joe Perches <joe@...ches.com>
To:	Tom Van Braeckel <tomvanbraeckel@...il.com>
Cc:	apw@...onical.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] checkpatch: support more uppercase $logFunctions

On Thu, 2015-03-19 at 09:26 +0100, Tom Van Braeckel wrote:
> Add support for uppercase logging function names (so that they may
> exceed 80 cols) and regroup the matched expressions more logically.
> 
> Previously, WARN, WARN_RATELIMIT, WARN_ONCE were already supported but
> many other uppercase logging functions were not and this caused
> unfixable checkpatch warnings (an example: drivers/bluetooth/btusb.c)

I think BT_DBG is a poor macro as it's just

#define BT_DBG(fmt, ...) pr_debug(fmt "\n", ##__VA_ARGS__)

and I'd rather see a treewide sed for that to pr_debug


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