public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Straube <straube.linux@gmail.com>
To: Joe Perches <joe@perches.com>, gregkh@linuxfoundation.org
Cc: ajay.kathat@microchip.com, adham.abozaeid@microchip.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wilc1000: correct inconsistent indenting
Date: Thu, 29 Nov 2018 14:45:04 +0100	[thread overview]
Message-ID: <325d0ffa-85a2-7fcd-30ae-798c0c2c06dc@gmail.com> (raw)
In-Reply-To: <d93b32c5861eb5ae552b2ed3fc65c087dc7fa328.camel@perches.com>

On 11/29/18 7:24 AM, Joe Perches wrote:
> On Wed, 2018-11-28 at 19:17 +0100, Michael Straube wrote:
>> Correct inconsistent indenting reported by smatch.
> []
>> diff --git a/drivers/staging/wilc1000/wilc_spi.c b/drivers/staging/wilc1000/wilc_spi.c
> []
>> @@ -963,7 +963,7 @@ static int wilc_spi_read_int(struct wilc *wilc, u32 *int_status)
>>   			dev_err(&spi->dev,
>>   				"Unexpected interrupt(2):j=%d,tmp=%x,mask=%x\n",
>>   				j, tmp, unknown_mask);
>> -				happened = 1;
>> +			happened = 1;s a
>>   		}
>>   
>>   		j++;
> 
> Perhaps a little refactoring instead
> ---
>   drivers/staging/wilc1000/wilc_spi.c | 12 +++++-------
>   1 file changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/wilc_spi.c b/drivers/staging/wilc1000/wilc_spi.c
> index 35ff432587fe..a38ddb1f0a1f 100644
> --- a/drivers/staging/wilc1000/wilc_spi.c
> +++ b/drivers/staging/wilc1000/wilc_spi.c
> @@ -927,7 +927,8 @@ static int wilc_spi_read_int(struct wilc *wilc, u32 *int_status)
>   	int ret;
>   	u32 tmp;
>   	u32 byte_cnt;
> -	int happened, j;
> +	bool unexpected_irq;
> +	int j;
>   	u32 unknown_mask;
>   	u32 irq_flags;
>   	int k = IRG_FLAGS_OFFSET + 5;
> @@ -947,8 +948,6 @@ static int wilc_spi_read_int(struct wilc *wilc, u32 *int_status)
>   
>   	j = 0;
>   	do {
> -		happened = 0;
> -
>   		wilc_spi_read_reg(wilc, 0x1a90, &irq_flags);
>   		tmp |= ((irq_flags >> 27) << IRG_FLAGS_OFFSET);
>   
> @@ -959,15 +958,14 @@ static int wilc_spi_read_int(struct wilc *wilc, u32 *int_status)
>   
>   		unknown_mask = ~((1ul << spi_priv->nint) - 1);
>   
> -		if ((tmp >> IRG_FLAGS_OFFSET) & unknown_mask) {
> +		unexpected_irq = (tmp >> IRG_FLAGS_OFFSET) & unknown_mask;
> +		if (unexpected_irq)
>   			dev_err(&spi->dev,
>   				"Unexpected interrupt(2):j=%d,tmp=%x,mask=%x\n",
>   				j, tmp, unknown_mask);
> -				happened = 1;
> -		}
>   
>   		j++;
> -	} while (happened);
> +	} while (unexpected_irq);
>   
>   	*int_status = tmp;
>   
> 
Hi Joe,

that looks good to me.
Naming the loop condition unexpected_irq also improves readability.

I will send a new patch, thanks.
Michael

      reply	other threads:[~2018-11-29 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 18:17 [PATCH] staging: wilc1000: correct inconsistent indenting Michael Straube
2018-11-29  6:24 ` Joe Perches
2018-11-29 13:45   ` Michael Straube [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=325d0ffa-85a2-7fcd-30ae-798c0c2c06dc@gmail.com \
    --to=straube.linux@gmail.com \
    --cc=adham.abozaeid@microchip.com \
    --cc=ajay.kathat@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --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