public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cheah Kok Cheong <thrust73@gmail.com>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: hsweeten@visionengravers.com, gregkh@linuxfoundation.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: drivers: comedi_test: Avoid multiple line dereference
Date: Tue, 21 Feb 2017 00:02:05 +0800	[thread overview]
Message-ID: <20170220160205.GA4017@linux-Precision-WorkStation-T5500> (raw)
In-Reply-To: <ed7277eb-bf16-d90f-0697-7a421bb3910d@mev.co.uk>

On Mon, Feb 20, 2017 at 10:03:39AM +0000, Ian Abbott wrote:
> On 20/02/17 08:28, Cheah Kok Cheong wrote:
> >Fix checkpatch warning "Avoid multiple line dereference"
> >using a local variable to avoid line wrap.
> >
> >Signed-off-by: Cheah Kok Cheong <thrust73@gmail.com>
> >---
> > drivers/staging/comedi/drivers/comedi_test.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> >diff --git a/drivers/staging/comedi/drivers/comedi_test.c b/drivers/staging/comedi/drivers/comedi_test.c
> >index 2a063f0..fde83e0 100644
> >--- a/drivers/staging/comedi/drivers/comedi_test.c
> >+++ b/drivers/staging/comedi/drivers/comedi_test.c
> >@@ -480,11 +480,9 @@ static void waveform_ao_timer(unsigned long arg)
> > 			/* output the last scan */
> > 			for (i = 0; i < cmd->scan_end_arg; i++) {
> > 				unsigned int chan = CR_CHAN(cmd->chanlist[i]);
> >+				unsigned short d = devpriv->ao_loopbacks[chan];
> >
> >-				if (comedi_buf_read_samples(s,
> >-							    &devpriv->
> >-							     ao_loopbacks[chan],
> >-							    1) == 0) {
> >+				if (!comedi_buf_read_samples(s, &d, 1)) {
> > 					/* unexpected underrun! (cancelled?) */
> > 					async->events |= COMEDI_CB_OVERFLOW;
> > 					goto underrun;
> >
> 
> NAK.  This leaves devpriv->ao_loopbacks[chan] unchanged.
> 

Thanks for pointing this out. In that case will assigning the variable to
devpriv->ao_loopbacks[chan] be acceptable? Please review below snippet.

Otherwise I'll just drop the variable and adjust the lines to avoid
checkpatch warning.

Sorry for the inconvenience caused.

[ Snip ]

			/* output the last scan */
			for (i = 0; i < cmd->scan_end_arg; i++) {
				unsigned int chan = CR_CHAN(cmd->chanlist[i]);
				unsigned short data;

				if (!comedi_buf_read_samples(s, &data, 1)) {
					/* unexpected underrun! (cancelled?) */
					async->events |= COMEDI_CB_OVERFLOW;
					goto underrun;
				}

				devpriv->ao_loopbacks[chan] = data;
			}
			/* advance time of last scan */

[ Snip ]

Thks.
Brgds,
CheahKC

  reply	other threads:[~2017-02-20 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20  8:28 [PATCH] Staging: comedi: drivers: comedi_test: Avoid multiple line dereference Cheah Kok Cheong
2017-02-20 10:03 ` Ian Abbott
2017-02-20 16:02   ` Cheah Kok Cheong [this message]
2017-02-20 17:36     ` Ian Abbott
2017-02-21  9:33       ` Cheah Kok Cheong
2017-02-21 10:12         ` Ian Abbott
2017-02-21 10:20           ` Valentin Rothberg
2017-02-21 16:31             ` Cheah Kok Cheong
2017-02-21 17:22               ` Joe Perches
2017-02-22  8:30                 ` Valentin Rothberg

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=20170220160205.GA4017@linux-Precision-WorkStation-T5500 \
    --to=thrust73@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --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