All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Valentin Vidic <Valentin.Vidic@CARNet.hr>,
	David Miller <davem@davemloft.net>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	"Marcin Ciupak" <marcin.s.ciupak@gmail.com>,
	"Marcus Wolf" <linux@wolf-entwicklungen.de>,
	"Simon Sandström" <simon@nikanor.nu>
Subject: Re: [PATCH] staging: pi433: remove unnecessary parentheses
Date: Tue, 09 Jan 2018 11:21:37 -0800	[thread overview]
Message-ID: <1515525697.9619.100.camel@perches.com> (raw)
In-Reply-To: <20180109143148.GB608@kroah.com>

On Tue, 2018-01-09 at 15:31 +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 08, 2018 at 06:38:55PM +0100, Valentin Vidic wrote:
> > Fixes checkpatch warnings:
> >   CHECK: Unnecessary parentheses around 'mantisse != mantisse16'
> >   CHECK: Unnecessary parentheses around 'mantisse != mantisse20'
> >   CHECK: Unnecessary parentheses around 'mantisse != mantisse24'
[]
> > diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c
[]
> > @@ -391,9 +391,9 @@ static int rf69_set_bandwidth_intern(struct spi_device *spi, u8 reg,
> >  		return -EINVAL;
> >  	}
> >  
> > -	if ((mantisse != mantisse16) &&
> > -	    (mantisse != mantisse20) &&
> > -	    (mantisse != mantisse24)) {
> > +	if (mantisse != mantisse16 &&
> > +	    mantisse != mantisse20 &&
> > +	    mantisse != mantisse24) {
> 
> I'm getting really tired of seeing this checkpatch warning, when it's a
> major pain.

Your idea of major pain and mine differ a bit.

> Joe, can you please turn these off.  Patches like this will force people
> to have to remember that != is higher precidence than &&.

As it's not just 1 precedence level but 4 and 5, it
really shouldn't be that hard to remember.

> The original code here was just fine.

And I don't really disagree with you.

David Miller has a preference for the parenthesis free
style. I believe he mentioned it sometime in August 2017
but I can't find it right now.

Anyway, perhaps
---
 scripts/checkpatch.pl | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index d2464058ab5d..3a7499de2c2d 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -4526,7 +4526,9 @@ sub process {
 		}
 
 # check for unnecessary parentheses around comparisons in if uses
-		if ($^V && $^V ge 5.10.0 && defined($stat) &&
+# when !drivers/staging or the command-line uses --strict
+		if (($realfile !~ m@^(?:drivers/staging/)@ || $check_orig) &&
+		    $^V && $^V ge 5.10.0 && defined($stat) &&
 		    $stat =~ /(^.\s*if\s*($balanced_parens))/) {
 			my $if_stat = $1;
 			my $test = substr($2, 1, -1);

  reply	other threads:[~2018-01-09 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 17:38 [PATCH] staging: pi433: remove unnecessary parentheses Valentin Vidic
2018-01-09 14:31 ` Greg Kroah-Hartman
2018-01-09 19:21   ` Joe Perches [this message]
2018-01-09 19:28     ` Greg Kroah-Hartman
2018-01-09 19:42       ` Joe Perches
2018-01-10  8:44         ` Greg Kroah-Hartman
2018-01-10  9:05           ` Joe Perches
2018-01-10  9:49             ` marcus.wolf

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=1515525697.9619.100.camel@perches.com \
    --to=joe@perches.com \
    --cc=Valentin.Vidic@CARNet.hr \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@wolf-entwicklungen.de \
    --cc=marcin.s.ciupak@gmail.com \
    --cc=simon@nikanor.nu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.