From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Stenglein <mark@stengle.in>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: most: Adds parentheses around macros with complex values
Date: Thu, 23 Mar 2017 09:59:24 +0100 [thread overview]
Message-ID: <20170323085924.GA19222@kroah.com> (raw)
In-Reply-To: <20170323083838.29565-1-mark@stengle.in>
On Thu, Mar 23, 2017 at 04:38:38AM -0400, Mark Stenglein wrote:
> Fixes three instances of the following checklist error:
> - ERROR: Macros with complex values should be enclosed
> in parentheses
>
> Simply adds parentheses around the macros to fix the problem.
>
> Signed-off-by: Mark Stenglein <mark@stengle.in>
> ---
> drivers/staging/most/mostcore/core.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/most/mostcore/core.c b/drivers/staging/most/mostcore/core.c
> index 191404bc5906..13e65f149d68 100644
> --- a/drivers/staging/most/mostcore/core.c
> +++ b/drivers/staging/most/mostcore/core.c
> @@ -341,8 +341,8 @@ static ssize_t show_channel_starving(struct most_c_obj *c,
> return snprintf(buf, PAGE_SIZE, "%d\n", c->is_starving);
> }
>
> -#define create_show_channel_attribute(val) \
> - static MOST_CHNL_ATTR(val, 0444, show_##val, NULL)
> +#define(create_show_channel_attribute(val) \
> + static MOST_CHNL_ATTR(val, 0444, show_##val, NULL))
I don't think this does what you think it does. Did you test build
this???
Please learn C before working on kernel code, the kernel is not a place
to learn it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-23 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 8:38 [PATCH] staging: most: Adds parentheses around macros with complex values Mark Stenglein
2017-03-23 8:59 ` Greg KH [this message]
2017-03-25 7:26 ` kbuild test robot
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=20170323085924.GA19222@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@stengle.in \
/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