linux-kernel - New 2.6.36 checkpatch complaints about leading whitespace

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

Date:	Sat, 30 Oct 2010 11:35:22 +0200
From:	Bart Van Assche <bvanassche@....org>
To:	Andy Whitcroft <apw@...onical.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Vladislav Bolkhovitin <vst@...b.net>
Subject: New 2.6.36 checkpatch complaints about leading whitespace

Hello Andy,

Apparently the checkpatch.pl script as included in 2.6.36 complains if
continued lines start with whitespace. An example:

[ ... ]
+#if defined(MACRO_NAME_1) || defined(MACRO_NAME_2) \
+  || defined(MACRO_NAME_3)
[ ... ]

checkpatch.pl reports the following warning for the above patch excerpt:

WARNING: please, no space for starting a line,
                                excluding comments

Is that a feature or an unintended side effect of recent checkpatch changes ?

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