public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@shadowen.org>, linux-kernel@vger.kernel.org
Subject: Re: checkpatch and kernel/sched.c
Date: Mon, 1 Oct 2007 12:44:06 +0200	[thread overview]
Message-ID: <20071001104406.GC15488@elte.hu> (raw)
In-Reply-To: <20071001003007.4e90143b.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> > > WARNING: braces {} are not necessary for single statement blocks
> > > #5706: FILE: home/apw/git/linux-2.6/kernel/sched.c:5703:
> > > +	if (parent->groups == parent->groups->next) {
> > > +		pflags &= ~(SD_LOAD_BALANCE |
> > > +				SD_BALANCE_NEWIDLE |
> > > +				SD_BALANCE_FORK |
> > > +				SD_BALANCE_EXEC |
> > > +				SD_SHARE_CPUPOWER |
> > > +				SD_SHARE_PKG_RESOURCES);
> > > +	}
> > > 
> > > Ok, this one is "correct" at least for the rules as I have them.
> > > Perhaps the message should not be emitted for very long blocks?
> > 
> > If a statement is not single-line, then braces _are_ fine. Where does 
> > CodingStyle say that it's not fine?
> 
> I'd disagree with checkpatch there.  Again, it might be hard to fix.  
> Wanna rename it to checkpatch-and-suggest-stuff-to-think-about.pl?

i think checkpatch.pl is quite close to its most useful purpose and 
role: that of a reliable tool that i can use in an automated fashion 
too, with only very rare false positive - and not the current 50%-80% 
false positives rate. (And i'm fighting hard for Andy to realize the 
true scope and purpose of this script ;-)

	Ingo

  parent reply	other threads:[~2007-10-01 10:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070928105345.GC18163@shadowen.org>
2007-10-01  6:44 ` checkpatch and kernel/sched.c Ingo Molnar
2007-10-01  7:30   ` Andrew Morton
2007-10-01  7:48     ` Avi Kivity
2007-10-01  7:39       ` Andrew Morton
2007-10-01 10:39         ` Ingo Molnar
2007-10-01  7:50     ` Sam Ravnborg
2007-10-01 10:37     ` Ingo Molnar
2007-10-01 10:44     ` Ingo Molnar [this message]
2007-10-01 12:34     ` Andy Whitcroft
2007-10-02  4:34     ` Willy Tarreau
2007-10-02  5:18       ` [patch] printk: add KERN_CONT annotation Ingo Molnar
2007-10-02 10:04         ` Jörn Engel
2007-10-02 15:41         ` Joe Perches
2007-10-02 15:45           ` Jan Engelhardt
2007-10-02 16:03             ` Joe Perches
2007-10-02 16:07               ` Jan Engelhardt
2007-10-04 20:43         ` Andrew Morton
2007-10-04 20:52           ` Ingo Molnar

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=20071001104406.GC15488@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --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