public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>, Joe Perches <joe@perches.com>
Cc: Chase Southwood <chase.southwood@yahoo.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Ian Abbott <ian.abbott@mev.co.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staging: comedi: move trailing statement to next line in ni_mio_common.c
Date: Tue, 14 Jan 2014 11:45:38 +0000	[thread overview]
Message-ID: <52D52362.4080700@mev.co.uk> (raw)
In-Reply-To: <20140114072344.GL7444@mwanda>

On 2014-01-14 07:23, Dan Carpenter wrote:
> On Mon, Jan 13, 2014 at 07:16:14PM -0800, Joe Perches wrote:
>> On Mon, 2014-01-13 at 21:13 -0600, Chase Southwood wrote:
>>> This patch for ni_mio_common.c silences a checkpatch error due to a
>>> trailing statement.
>> []
>>> diff --git a/drivers/staging/comedi/drivers/ni_mio_common.c b/drivers/staging/comedi/drivers/ni_mio_common.c
>> []
>>> @@ -692,7 +692,8 @@ static void ni_clear_ai_fifo(struct comedi_device *dev)
>>>   		/*  Flush the 6143 data FIFO */
>>>   		ni_writel(0x10, AIFIFO_Control_6143);	/*  Flush fifo */
>>>   		ni_writel(0x00, AIFIFO_Control_6143);	/*  Flush fifo */
>>> -		while (ni_readl(AIFIFO_Status_6143) & 0x10) ;	/*  Wait for complete */
>>> +		while (ni_readl(AIFIFO_Status_6143) & 0x10)
>>> +			;	/*  Wait for complete */
>>
>> It's generally better to use timeouts too.
>
> Just to clarify what Joe is saying do:
>
> 		/*  Wait for complete */
> 		while (timemout < TIMEOUT) {
> 			if (ni_readl(AIFIFO_Status_6143) & 0x10)
> 				break;
> 			udelay(1);
> 		}
>
> I added in a delay...  The problem is that you'd probably have to look
> at the hardware spec to know what timeout to use or if the delay is
> needed.

Some longish timeout of, say, 10000 iterations (~ 0.01 seconds) would 
probably do as it's not that time critical.

We wouldn't expect code clean-up patches to have to deal with that sort 
of thing though.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

  reply	other threads:[~2014-01-14 11:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  3:13 [PATCH] Staging: comedi: move trailing statement to next line in ni_mio_common.c Chase Southwood
2014-01-14  3:16 ` Joe Perches
2014-01-14  7:23   ` Dan Carpenter
2014-01-14 11:45     ` Ian Abbott [this message]
2014-01-14 11:48 ` Ian Abbott
2014-01-14 19:38 ` [PATCH v2] Staging: comedi: convert while loop to timeout " Chase Southwood
2014-01-14 19:45   ` Joe Perches
2014-01-14 19:50   ` Greg KH
2014-01-14 21:31 ` [PATCH v3] " Chase Southwood
2014-01-14 23:10   ` Greg KH
2014-01-15  0:23 ` [PATCH v4] " Chase Southwood
2014-01-15  3:58   ` Greg KH
2014-01-15 10:29     ` Ian Abbott
2014-01-15 18:29     ` Hartley Sweeten
2014-01-16  2:30       ` Greg KH
2014-01-16 11:08         ` Ian Abbott
2014-01-15  5:15 ` [PATCH v5] " Chase Southwood
2014-01-15 10:38   ` Ian Abbott
2014-01-15 17:51 ` [PATCH v6] " Chase Southwood
2014-01-15 18:48   ` Hartley Sweeten
2014-01-15 19:22 ` [PATCH v7] " Chase Southwood
2014-01-16 11:30   ` Ian Abbott
2014-01-16 17:46     ` Chase Southwood
2014-01-16 18:27 ` [PATCH v8] " Chase Southwood
2014-01-17 13:12   ` Ian Abbott

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=52D52362.4080700@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=chase.southwood@yahoo.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ian.abbott@mev.co.uk \
    --cc=joe@perches.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