linux-kernel - Re: +patch Why these dot chars in scripts/checkpatch.pl?

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]

Message-Id: <bbde4dbb04c0d77f846f0ed706a81530@kernel.crashing.org>
Date:	Tue, 29 Apr 2008 11:51:52 +0200
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Paul Jackson <pj@....com>, Rogan Dawes <lists@...es.za.net>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	linux-kernel@...r.kernel.org
Subject: Re: +patch Why these dot chars in scripts/checkpatch.pl?

> Yeah I was under the missaprehension that whitespace was allowed after
> the # but not before.  That seems to be flawed.

It is true for K&R C (so with -traditional cpp mode), but indeed
false for ISO C.


Segher

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