public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Niranjan Dighe <niranjan.dighe@gmail.com>,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	charrer@alacritech.com, liodot@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Staging: slicoss: Fix checkpatch.pl issues
Date: Tue, 24 Mar 2015 13:27:52 -0700	[thread overview]
Message-ID: <1427228872.12126.8.camel@perches.com> (raw)
In-Reply-To: <20150324201429.GV10964@mwanda>

On Tue, 2015-03-24 at 23:14 +0300, Dan Carpenter wrote:
> On Wed, Mar 25, 2015 at 12:39:06AM +0530, Niranjan Dighe wrote:
> > The following files had coding style issues that I tried to address.
> > It was mostly about lines spanning more than 80 characters.
[]
> > diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c
[]
> > @@ -755,10 +756,10 @@ static bool slic_mac_filter(struct adapter *adapter,
> >  
> >  			while (mcaddr) {
> >  				if (ether_addr_equal(mcaddr->address,
> > -						     ether_frame->ether_dhost)) {
> > -					adapter->rcv_multicasts++;
> > -					netdev->stats.multicast++;
> > -					return true;
> > +					ether_frame->ether_dhost)) {
> > +						adapter->rcv_multicasts++;
> > +						netdev->stats.multicast++;
> > +						return true;
> >  				}
> >  				mcaddr = mcaddr->next;
> >  			}
> 
> Check patch likes the new code but the original is better for human
> beings.  Sorry.

The indentation isn't correct in the new code either.

That's actually a checkpatch defect because it's not
able to track deletion/insertion alignment well enough.

Niranjan, checkpatch is a brainless little tool.
Always use yours whenever using checkpatch.


      reply	other threads:[~2015-03-24 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 19:09 Staging: slicoss: Fix checkpatch.pl issues Niranjan Dighe
2015-03-24 19:26 ` Joe Perches
2015-03-24 20:14 ` Dan Carpenter
2015-03-24 20:27   ` Joe Perches [this message]

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=1427228872.12126.8.camel@perches.com \
    --to=joe@perches.com \
    --cc=charrer@alacritech.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liodot@gmail.com \
    --cc=niranjan.dighe@gmail.com \
    /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