public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andrii <tulup@mail.ru>
Cc: devel@driverdev.osuosl.org, sergio.paracuellos@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] staging: wlan-ng: fix avoid multiple line dereference warning reported by checkpatch.pl
Date: Sun, 12 Mar 2017 17:24:17 +0100	[thread overview]
Message-ID: <20170312162417.GA6843@kroah.com> (raw)
In-Reply-To: <20170312174733.455782d3@andrii-VirtualBox>

On Sun, Mar 12, 2017 at 05:47:33PM +0200, Andrii wrote:
> On Sun, 12 Mar 2017 16:42:07 +0100
> Greg KH <gregkh@linuxfoundation.org> wrote:
> 
> > On Sun, Mar 12, 2017 at 05:30:09PM +0200, Andrii wrote:
> > > Fixed three code style warnings (multiple line dereference) reported
> > > by checkpatch.pl script.
> > > 
> > > Signed-off-by: Andrii Vladyka <tulup@mail.ru>  
> > 
> > > diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c
> > > b/drivers/staging/wlan-ng/hfa384x_usb.c index 6134eba..a050748
> > > 100644 --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> > > +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
> > > @@ -1346,14 +1346,8 @@ hfa384x_docmd(struct hfa384x *hw,
> > >  	} else if (mode == DOWAIT) {
> > >  		struct usbctlx_cmd_completor completor;
> > >  
> > > -		result =
> > > -		    hfa384x_usbctlx_complete_sync(hw, ctlx,
> > > -
> > > init_cmd_completor(&completor,
> > > -
> > > &ctlx->
> > > -
> > > inbuf.
> > > -
> > > cmdresp,
> > > -
> > > &cmd->
> > > -
> > > result));
> > > +		result = hfa384x_usbctlx_complete_sync(hw, ctlx,
> > > +	init_cmd_completor(&completor, &ctlx->inbuf.cmdresp,
> > > &cmd->result))  
> > 
> > Hm, did you run your patch through checkpatch?  There's no way that
> > his code is correct :(
> > 
> > greg k-h
> 
> Yes, I did. The code is correct. Checkpatch now reports "Alignment
> should match open parenthesis" CHECK, which is obviously better than
> original WARNING.

Really?  No, it's much worse.  Indentation should be obvious when
looking at the code, right now this is just so wrong it hurts my brain
to look at (seriously, coding style is there for your brain, not because
we are crazy picky developers.)

Also you forgot a trailing ';' did that even compile?

thanks,

greg k-h

  reply	other threads:[~2017-03-12 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 20:39 [PATCH] staging: wlan-ng: fix checkpatch.pl code style warnings Andrii
2017-03-12 14:16 ` Greg KH
2017-03-12 15:30 ` [PATCHv2] staging: wlan-ng: fix avoid multiple line dereference warning reported by checkpatch.pl Andrii
2017-03-12 15:42   ` Greg KH
2017-03-12 15:47     ` Andrii
2017-03-12 16:24       ` Greg KH [this message]
2017-03-29  7:32   ` Greg KH

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=20170312162417.GA6843@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tulup@mail.ru \
    /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