All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh at linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH] staging: media: bcm2048: Fixed style error ERROR: Macros with complex values should be enclosed in parentheses found using scripts/checkpatch.pl
Date: Mon, 29 Apr 2019 19:46:44 +0200	[thread overview]
Message-ID: <20190429174644.GA21757@kroah.com> (raw)
In-Reply-To: <20190429171755.GA11268@arch>

On Mon, Apr 29, 2019 at 10:47:55PM +0530, Puranjay Mohan wrote:
> On Mon, Apr 29, 2019 at 09:34:41AM -0600, Shuah Khan wrote:
> > On 4/29/19 9:17 AM, Puranjay Mohan wrote:
> > > On Mon, Apr 29, 2019 at 04:56:35PM +0200, Greg KH wrote:
> > > > On Mon, Apr 29, 2019 at 08:20:02PM +0530, Puranjay Mohan wrote:
> > > > > Signed-off-by: Puranjay Mohan <puranjay12 at gmail.com>
> > > > > ---
> > > > 
> > > > I think your subject line needs a bit of work :)
> > > > 
> > > > Also, I can't take patches without any changelog text.
> > > > 
> > > > >   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 d9b02ff66259..599da6c977ed 100644
> > > > > --- a/drivers/staging/media/bcm2048/radio-bcm2048.c
> > > > > +++ b/drivers/staging/media/bcm2048/radio-bcm2048.c
> > > > > @@ -2000,7 +2000,7 @@ static ssize_t bcm2048_##prop##_read(struct device *dev,		\
> > > > >   	return sprintf(buf, mask "\n", value);				\
> > > > >   }
> > > > > -#define DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check)		\
> > > > > +#define (DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check))		\
> > > > >   property_write(prop, prop_type, mask, check)				\
> > > > >   property_read(prop, mask)						\
> > > > 
> > > > Wait, did you build this patch?  Are you sure it is doing what you think
> > > > it is doing?
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > 
> > > It is my first patch ever, can you guide me on how to resend the patch
> > > with the corrections.
> > > After adding the parentheses around the Macro, the Error was not showing
> > > up with the checkpatch.pl so I thought it corrected it.
> > > 
> > Did you build and run tests to make sure you change works?
> > 
> > Please go through the following to understand all about sending your first
> > patch.
> > 
> > https://wiki.linuxfoundation.org/lkmp/lkmp_getting_started
> > 
> > This should tell you the steps to follow before sending the patch.
> > 
> > thanks,
> > -- Shuah
> 
> 
> I built the driver and this change caused a compilation error. Sorry for
> sending a wrong patch.
> Please help me in solving the checkpatch.pl error.
> 
> ERROR: Macros with complex values should be enclosed in parentheses
> #2003: FILE: drivers/staging/media/bcm2048/radio-bcm2048.c:2003:
> +#define DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check)		\
> +property_write(prop, prop_type, mask, check)				\
> +property_read(prop, mask)						\
> +

How well do you understand C and how macros work with it?

Do you see anything wrong with this code?  What happens if you pass in
something "unusual" for one of those parameters?

Also, always remember that checkpatch.pl is a dumb perl script,
sometimes it is not correct, and may be ignored for some types of
things.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH] staging: media: bcm2048: Fixed style error ERROR: Macros with complex values should be enclosed in parentheses found using scripts/checkpatch.pl
Date: Mon, 29 Apr 2019 19:46:44 +0200	[thread overview]
Message-ID: <20190429174644.GA21757@kroah.com> (raw)
Message-ID: <20190429174644.NX5YHBg5mFxMcayb9VqYM7OmTRY9NMlfHOyXFgPQDp8@z> (raw)
In-Reply-To: <20190429171755.GA11268@arch>

On Mon, Apr 29, 2019 at 10:47:55PM +0530, Puranjay Mohan wrote:
> On Mon, Apr 29, 2019 at 09:34:41AM -0600, Shuah Khan wrote:
> > On 4/29/19 9:17 AM, Puranjay Mohan wrote:
> > > On Mon, Apr 29, 2019 at 04:56:35PM +0200, Greg KH wrote:
> > > > On Mon, Apr 29, 2019 at 08:20:02PM +0530, Puranjay Mohan wrote:
> > > > > Signed-off-by: Puranjay Mohan <puranjay12 at gmail.com>
> > > > > ---
> > > > 
> > > > I think your subject line needs a bit of work :)
> > > > 
> > > > Also, I can't take patches without any changelog text.
> > > > 
> > > > >   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 d9b02ff66259..599da6c977ed 100644
> > > > > --- a/drivers/staging/media/bcm2048/radio-bcm2048.c
> > > > > +++ b/drivers/staging/media/bcm2048/radio-bcm2048.c
> > > > > @@ -2000,7 +2000,7 @@ static ssize_t bcm2048_##prop##_read(struct device *dev,		\
> > > > >   	return sprintf(buf, mask "\n", value);				\
> > > > >   }
> > > > > -#define DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check)		\
> > > > > +#define (DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check))		\
> > > > >   property_write(prop, prop_type, mask, check)				\
> > > > >   property_read(prop, mask)						\
> > > > 
> > > > Wait, did you build this patch?  Are you sure it is doing what you think
> > > > it is doing?
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > 
> > > It is my first patch ever, can you guide me on how to resend the patch
> > > with the corrections.
> > > After adding the parentheses around the Macro, the Error was not showing
> > > up with the checkpatch.pl so I thought it corrected it.
> > > 
> > Did you build and run tests to make sure you change works?
> > 
> > Please go through the following to understand all about sending your first
> > patch.
> > 
> > https://wiki.linuxfoundation.org/lkmp/lkmp_getting_started
> > 
> > This should tell you the steps to follow before sending the patch.
> > 
> > thanks,
> > -- Shuah
> 
> 
> I built the driver and this change caused a compilation error. Sorry for
> sending a wrong patch.
> Please help me in solving the checkpatch.pl error.
> 
> ERROR: Macros with complex values should be enclosed in parentheses
> #2003: FILE: drivers/staging/media/bcm2048/radio-bcm2048.c:2003:
> +#define DEFINE_SYSFS_PROPERTY(prop, prop_type, mask, check)		\
> +property_write(prop, prop_type, mask, check)				\
> +property_read(prop, mask)						\
> +

How well do you understand C and how macros work with it?

Do you see anything wrong with this code?  What happens if you pass in
something "unusual" for one of those parameters?

Also, always remember that checkpatch.pl is a dumb perl script,
sometimes it is not correct, and may be ignored for some types of
things.

thanks,

greg k-h

  reply	other threads:[~2019-04-29 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 14:50 [Linux-kernel-mentees] [PATCH] staging: media: bcm2048: Fixed style error ERROR: Macros with complex values should be enclosed in parentheses found using scripts/checkpatch.pl puranjay12
2019-04-29 14:50 ` Puranjay Mohan
2019-04-29 14:56 ` greg
2019-04-29 14:56   ` Greg KH
2019-04-29 15:17   ` puranjay12
2019-04-29 15:17     ` Puranjay Mohan
2019-04-29 15:34     ` skhan
2019-04-29 15:34       ` Shuah Khan
2019-04-29 17:17       ` puranjay12
2019-04-29 17:17         ` Puranjay Mohan
2019-04-29 17:46         ` gregkh [this message]
2019-04-29 17:46           ` Greg KH

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=20190429174644.GA21757@kroah.com \
    --to=unknown@example.com \
    /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.