[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_ZknVmAnoa=+BA9Q+BSJ_dKwtBWWXHqZyJ_BH=FppqGLpFUg@mail.gmail.com>
Date: Mon, 28 Dec 2015 16:33:27 +0200
From: Andrey Utkin <andrey.utkin@...p.bluecherry.net>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kernel-janitors <kernel-janitors@...r.kernel.org>,
"kernel-mentors@...enic.com" <kernel-mentors@...enic.com>,
Linux Media <linux-media@...r.kernel.org>,
devel@...verdev.osuosl.org
Cc: andrey.od.utkin@...il.com
Subject: On Lindent shortcomings and massive style fixing
After some iterations of checkpatch.pl, on a new developed driver
(tw5864), now I have the following:
$ grep 'WARNING\|ERROR' /src/checkpatch.tw5864 | sort | uniq -c
31 ERROR: do not use C99 // comments
147 WARNING: Block comments use a trailing */ on a separate line
144 WARNING: Block comments use * on subsequent lines
435 WARNING: line over 80 characters
At this point, Lindent was already used, and checkpatch.pl warnings
introduced by Lindent itself were fixed. Usage of "indent
--linux-style" (which behaves differently BTW) doesn't help anymore,
too.
Could anybody please advise how to sort out these issues
automatically, because they look like perfectly solvable in automated
fashion. Of course manual work would result in more niceness, but I am
not eager to go through hundreds of place of code just to fix "over 80
characters" issues now.
First one ("do not use C99 // comments") looks easy with regexps, but
the other are not.
Is there any known improvements or successors for Lindent? Or could we
get indent/Lindent improved if we collect some money for this task?
If anybody wants to look at actual code, here it is:
https://github.com/bluecherrydvr/linux.git , branch tw5864_stable,
drivers/staging/media/tw5864
Current output of "checkpatch.pl -f" for all source files in the
driver is here:
https://gist.github.com/andrey-utkin/12295148475e34ef948b
Thanks in advance.
--
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/
Powered by blists - more mailing lists