linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/4] staging:iio: Don't compare boolean values with true/false
Date: Fri, 19 Oct 2012 18:59:08 +0100	[thread overview]
Message-ID: <508194EC.4050702@cam.ac.uk> (raw)
In-Reply-To: <5081941A.8050305@metafoo.de>

On 10/19/2012 06:55 PM, Lars-Peter Clausen wrote:
> On 10/19/2012 05:24 PM, Jonathan Cameron wrote:
>> On 10/18/2012 03:43 PM, Lars-Peter Clausen wrote:
>>> Fixes the following coccicheck warnings:
>>> 	drivers/staging/iio/accel/lis3l02dq_ring.c:240:5-10: WARNING: Comparison to bool
>>> 	drivers/staging/iio/iio_dummy_evgen.c:111:6-25: WARNING: Comparison to bool
>>>
>>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>> Can't say I can summon much enthusiasm for this patch..
> 
> Me neither, that's why I did not fix this up for the DAC drivers when I moved
> them out of staging. But it turns out that existing coccicheck errors can cause
> false positives in Fengguang Wu automated commit test scripts. We've seen a few
> of these in the past. So I've to decided to just fix all coccicheck
> warnings/error for IIO to avoid further false positives.
Fair enough and aiming for a clean coccicheck, smatch, sparse set makes it easier
to spot anything real that occurs locally. Also this is the correct time to do
this sort of stuff - nothing particularly big in the way of abi changes queued up
for these to cause fuzz in (for once ;)
> 
>> Added to togreg branch.
> 
> Thanks.
> 
>>> ---
>>>  drivers/staging/iio/accel/lis3l02dq_ring.c |    2 +-
>>>  drivers/staging/iio/iio_dummy_evgen.c      |    2 +-
>>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/staging/iio/accel/lis3l02dq_ring.c b/drivers/staging/iio/accel/lis3l02dq_ring.c
>>> index fa4190d..ee887e9 100644
>>> --- a/drivers/staging/iio/accel/lis3l02dq_ring.c
>>> +++ b/drivers/staging/iio/accel/lis3l02dq_ring.c
>>> @@ -237,7 +237,7 @@ static int lis3l02dq_data_rdy_trigger_set_state(struct iio_trigger *trig,
>>>  	u8 t;
>>>  
>>>  	__lis3l02dq_write_data_ready_config(indio_dev, state);
>>> -	if (state == false) {
>>> +	if (!state) {
>>>  		/*
>>>  		 * A possible quirk with the handler is currently worked around
>>>  		 * by ensuring outstanding read events are cleared.
>>> diff --git a/drivers/staging/iio/iio_dummy_evgen.c b/drivers/staging/iio/iio_dummy_evgen.c
>>> index 74e24e8..132d278 100644
>>> --- a/drivers/staging/iio/iio_dummy_evgen.c
>>> +++ b/drivers/staging/iio/iio_dummy_evgen.c
>>> @@ -108,7 +108,7 @@ int iio_dummy_evgen_get_irq(void)
>>>  
>>>  	mutex_lock(&iio_evgen->lock);
>>>  	for (i = 0; i < IIO_EVENTGEN_NO; i++)
>>> -		if (iio_evgen->inuse[i] == false) {
>>> +		if (!iio_evgen->inuse[i]) {
>>>  			ret = iio_evgen->base + i;
>>>  			iio_evgen->inuse[i] = true;
>>>  			break;
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2012-10-19 17:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 14:43 [PATCH 1/4] staging:iio: Don't compare boolean values with true/false Lars-Peter Clausen
2012-10-18 14:43 ` [PATCH 2/4] staging:iio:lpc32xx_adc: Use resource_size instead of opencoding it Lars-Peter Clausen
2012-10-18 16:16   ` Roland Stigge
2012-10-19 15:26     ` Jonathan Cameron
2012-10-18 14:43 ` [PATCH 3/4] iio: Don't compare boolean values to true/false Lars-Peter Clausen
2012-10-19 15:27   ` Jonathan Cameron
2012-10-18 14:43 ` [PATCH 4/4] iio: at91_adc: Use devm_kcalloc to allocate arrays Lars-Peter Clausen
2012-10-19  8:54   ` Maxime Ripard
2012-10-19 15:32   ` Jonathan Cameron
2012-10-19 15:24 ` [PATCH 1/4] staging:iio: Don't compare boolean values with true/false Jonathan Cameron
2012-10-19 17:55   ` Lars-Peter Clausen
2012-10-19 17:59     ` Jonathan Cameron [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=508194EC.4050702@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).