linux-kernel - Re: [PATCH 3/5] checkpatch: add a blacklist

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:	Tue, 06 Oct 2009 22:50:32 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Daniel Walker <dwalker@...o99.com>
Cc:	Andy Whitcroft <apw@...onical.com>, Li Zefan <lizf@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH 3/5] checkpatch: add a blacklist

Daniel Walker <dwalker@...o99.com> writes:

> In terms of the list getting long or not, your basically in control of
> it since you maintain checkpatch .. If you leave it without some sort of
> blacklist, then you end up with whole sections of code where the
> developers don't use checkpatch at all (or very little)..

Why? I routinely ignore specific warnings from checkpatch while paying
attention to other ones. That's precisely what one should expect if the
code in question technically violates the common style (or whatever is
it). I don't think we need exceptions in the checkpatch as they would
make it less useful and less reliable.
-- 
Krzysztof Halasa
--
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/