linux-kernel - [PATCH] [TRIVIAL] Remove invalid vi modeline

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

Message-ID: <1323086778.4555.40.camel@x61.thuisdomein>
Date:	Mon, 05 Dec 2011 13:06:18 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Jiri Kosina <trivial@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH] [TRIVIAL] Remove invalid vi modeline

Signed-off-by: Paul Bolle <pebolle@...cali.nl>
---
0) Opening lib/decompress_bunzip2.c with vim triggers this warning:
    "lib/decompress_bunzip2.c" 756L, 24002C
    Error detected while processing modelines:
    line    1:
    E521: Number required after =: sw =
    Press ENTER or type command to continue

1) Since the Linux kernel coding style disallows modelines this invalid
modeline can simply be removed. But perhaps you prefer a (series of)
patch(es) that removes all modelines. A quick grep of the tree suggests
that will be a lot of (tedious) work. But it's up to you, of course.

2) vim tested only.

 lib/decompress_bunzip2.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/lib/decompress_bunzip2.c b/lib/decompress_bunzip2.c
index a7b80c1..7ed5e32 100644
--- a/lib/decompress_bunzip2.c
+++ b/lib/decompress_bunzip2.c
@@ -1,4 +1,3 @@
-/* vi: set sw = 4 ts = 4: */
 /*	Small bzip2 deflate implementation, by Rob Landley (rob@...dley.net).
 
 	Based on bzip2 decompression code by Julian R Seward (jseward@....org),
-- 
1.7.7.3

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