public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Joel Schopp <jschopp@austin.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update checkpatch.pl to version 0.10
Date: Fri, 5 Oct 2007 07:56:36 +0200	[thread overview]
Message-ID: <20071005055636.GA31111@elte.hu> (raw)
In-Reply-To: <20070928104935.GA606@elte.hu>


here is an update wrt. the latest checkpatch.pl-next version 
(v11-to-be), about kernel/sched.c warnings:

>   size                          # warnings
>   ----------------------------------------
>   25383  checkpatch.pl.v6       5
>   26038  checkpatch.pl.v7       6
>   29603  checkpatch.pl.v8       65
>   31160  checkpatch.pl.v9       24
>   34950  checkpatch.pl.v10      28

    35948  checkpatch.pl.v11pre   11

so things are heading in the right direction :)

of those 11 warnings, 6 are correct warnings (4 will be solved via 
KERN_CONT, 1 will be solved via a proper include file, and 1 is an 
overlength line), 4 are borderline warnings (easily fixed) and only one 
is a false positive! So v11-to-be gets the "best checkpatch.pl ever" 
badge from me :)

The false positive is:

  ERROR: need consistent spacing around '*' (ctx:WxV)
  #5322: 
  +static ctl_table *sd_alloc_ctl_cpu_table(int cpu)
                    ^

i think checkpatch.pl mistook this function definition as an arithmetic 
expression?

But, there's a cleanliness bug underlying this false positive: 
'ctl_table' is a typedef, and it would be cleaner to use 'struct 
ctl_table' thoughout the kernel. When running checkpatch.pl over 
include/linux/sysctl.h, it warns about the typedef:

  WARNING: do not add new typedefs
  #944: 
  +typedef struct ctl_table ctl_table;

(but mistaking that function for an arithmetic expression is still a bug 
i think.)

nice work Andy!

	Ingo

  parent reply	other threads:[~2007-10-05  5:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 15:00 [PATCH] update checkpatch.pl to version 0.10 Andy Whitcroft
2007-09-28  8:40 ` Ingo Molnar
2007-09-28  9:01   ` Andrew Morton
2007-09-28  9:22     ` Andy Whitcroft
2007-09-28  9:39       ` Ingo Molnar
2007-09-28 10:00         ` Andy Whitcroft
2007-09-28 10:46           ` Christian Borntraeger
2007-09-28 11:03             ` WANG Cong
2007-09-28 14:19               ` Jan Engelhardt
2007-09-28 16:57                 ` Randy Dunlap
2007-09-28 10:49           ` Ingo Molnar
2007-09-28 13:21             ` Andy Whitcroft
2007-09-28 13:37               ` Pekka Enberg
2007-09-28 14:02                 ` Andy Whitcroft
2007-09-28 15:50               ` Joel Schopp
2007-09-28 17:26               ` Randy Dunlap
2007-09-28 17:46               ` Andrew Morton
2007-09-29  9:22                 ` Andy Whitcroft
2007-10-05  5:56             ` Ingo Molnar [this message]
2007-09-28 16:51           ` Sam Ravnborg
2007-09-28  9:44     ` Ingo Molnar
2007-09-28  9:52   ` Andy Whitcroft

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=20071005055636.GA31111@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.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