All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Tabrez khan <khan.tabrez21@gmail.com>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:bcm2048 : Add parentheses around  variable x
Date: Fri, 3 Feb 2017 07:55:55 -0200	[thread overview]
Message-ID: <20170203075555.3038fb36@vento.lan> (raw)
In-Reply-To: <1480758266-6160-1-git-send-email-khan.tabrez21@gmail.com>

Em Sat,  3 Dec 2016 15:14:26 +0530
Tabrez khan <khan.tabrez21@gmail.com> escreveu:

> Add parentheses around variable x for the readability purpose.
> 
> This warning was found using checkpatch.pl.
> 
> Signed-off-by: Tabrez khan <khan.tabrez21@gmail.com>
> ---
>  drivers/staging/media/bcm2048/radio-bcm2048.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/media/bcm2048/radio-bcm2048.c b/drivers/staging/media/bcm2048/radio-bcm2048.c
> index 4d9bd02..2f28dd0 100644
> --- a/drivers/staging/media/bcm2048/radio-bcm2048.c
> +++ b/drivers/staging/media/bcm2048/radio-bcm2048.c
> @@ -185,7 +185,7 @@
>  #define v4l2_to_dev(f)	((f * BCM2048_FREQV4L2_MULTI) / BCM2048_FREQDEV_UNIT)
>  
>  #define msb(x)                  ((u8)((u16)x >> 8))
> -#define lsb(x)                  ((u8)((u16)x &  0x00FF))
> +#define lsb(x)                  ((u8)((u16)(x) &  0x00FF))

If you're willing to do that, you should do on all macros. Also,
plese remove the extra space before the hexa value.

>  #define compose_u16(msb, lsb)	(((u16)msb << 8) | lsb)
>  
>  #define BCM2048_DEFAULT_POWERING_DELAY	20



Thanks,
Mauro

  reply	other threads:[~2017-02-03  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03  9:44 [PATCH] staging:bcm2048 : Add parentheses around variable x Tabrez khan
2017-02-03  9:55 ` Mauro Carvalho Chehab [this message]
2017-02-03 10:12 ` Dan Carpenter
2017-02-15 17:26   ` Tabrez Khan

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=20170203075555.3038fb36@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=khan.tabrez21@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.