From: Adrian Bunk <bunk@kernel.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: apw@shadowen.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] checkpatch: relax spacing and line length
Date: Sun, 6 Apr 2008 13:08:26 +0300 [thread overview]
Message-ID: <20080406100826.GD30987@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <alpine.LNX.1.10.0804060653020.30794@fbirervta.pbzchgretzou.qr>
On Sun, Apr 06, 2008 at 06:54:54AM +0200, Jan Engelhardt wrote:
> ===
> total: 0 errors, 0 warnings, 36 lines checked
>
> d27a9f5.diff has no obvious style problems and is ready for submission.
> ===
> commit d27a9f5760fa231ab888f96e27355a001c88b239
> Author: Jan Engelhardt <jengelh@computergmbh.de>
> Date: Sun Apr 6 06:49:01 2008 +0200
>
> checkpatch: relax spacing and line length
>
> We all had the arguments about 80 columns, so here goes a relax.
> Checking for 95 (or perhaps something better?), but of course we
> print "80" in the output, because if you happened to get to 95, it's
> "really time" to break it.
No, it's really time to teach people that checkpatch is *not* a tool for
janitors.
It's a tool for patch submitters and maintainers that automates a part
of patch review.
When a patch has a few checkpatch warnings and the submitter can justify
them (since the code would otherwise look bad) *that is OK*.
But if your driver has over 2000 lines over 80 columns or many lines
over 95 columns it is not "really time to break it" - it is time to
check *why* your code has that many that long lines.
> This also relaxes the tab doctrine, because spaces DO make sense --
> especially when you view the code with a tab setting of not-8.
>...
In the kernel all tabs are 8 spaces wide.
When you view the code with a different setting that's your fault.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-06 10:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 4:54 Jan Engelhardt
2008-04-06 5:18 ` Andrew Morton
2008-04-06 11:52 ` Benny Halevy
2008-04-06 18:52 ` Joe Perches
2008-04-07 9:51 ` Boaz Harrosh
2008-04-06 10:08 ` Adrian Bunk [this message]
2008-04-06 11:08 ` Sam Ravnborg
2008-04-07 16:37 ` Benny Halevy
2008-04-08 17:12 ` Andy Whitcroft
2008-04-08 18:01 ` Andi Kleen
2008-04-09 8:19 ` Andy Whitcroft
2008-04-09 8:30 ` Andy Whitcroft
2008-04-09 8:46 ` Andi Kleen
2008-04-09 13:14 ` Andy Whitcroft
2008-04-09 13:18 ` Jan Engelhardt
2008-04-09 13:58 ` Andy Whitcroft
2008-04-09 16:53 ` Andrew Morton
2008-04-09 17:43 ` Andi Kleen
2008-04-09 20:07 ` Andy Whitcroft
2008-04-11 15:54 ` Andy Whitcroft
2008-04-09 15:14 ` Randy Dunlap
2008-04-09 12:10 ` Benny Halevy
2008-04-09 12:19 ` Benny Halevy
2008-04-09 13:25 ` Andy Whitcroft
2008-04-09 17:02 ` Benny Halevy
2008-04-09 17:27 ` Stefan Richter
2008-04-09 20:16 ` Andy Whitcroft
2008-04-10 23:52 ` SL Baur
2008-04-11 4:24 ` Jan Engelhardt
2008-04-12 0:26 ` Al Viro
2008-04-13 9:53 ` Benny Halevy
2008-04-13 15:18 ` Al Viro
2008-04-15 9:09 ` Benny Halevy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080406100826.GD30987@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®