From: Levente Kurusa <levex@linux.com>
To: Nicolas Del Piano <ndel314@gmail.com>, gregkh@linuxfoundation.org
Cc: aaro.koskinen@iki.fi, devendra.aaru@gmail.com,
raluca.oncioiu91@gmail.com, david.daney@cavium.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: octeon-usb: fixed a macro coding style issue
Date: Fri, 25 Apr 2014 15:42:35 +0200 [thread overview]
Message-ID: <535A664B.3000805@linux.com> (raw)
In-Reply-To: <1398433233-2749-1-git-send-email-ndel314@gmail.com>
Hi,
On 04/25/2014 03:40 PM, Nicolas Del Piano wrote:
> Fixed a coding style error, macros with comples values should be enclosed in parenthesis.
>
> Signed-off-by: Nicolas Del Piano <ndel314@gmail.com>
> ---
> drivers/staging/octeon-usb/octeon-hcd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/octeon-usb/octeon-hcd.c b/drivers/staging/octeon-usb/octeon-hcd.c
> index 8b8ce72..475ecc4 100644
> --- a/drivers/staging/octeon-usb/octeon-hcd.c
> +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> @@ -246,7 +246,7 @@ enum cvmx_usb_pipe_flags {
> };
>
> /* Normal prefetch that use the pref instruction. */
> -#define CVMX_PREFETCH(address, offset) asm volatile ("pref %[type], %[off](%[rbase])" : : [rbase] "d" (address), [off] "I" (offset), [type] "n" (0))
> +#define (CVMX_PREFETCH(address, offset) asm volatile ("pref %[type], %[off](%[rbase])" : : [rbase] "d" (address), [off] "I" (offset), [type] "n" (0)))
Not that way around! :-)
The parantheses should be around the code block not the
name block.
--
Regards,
Levente Kurusa
PGP: 4EF5D641
next prev parent reply other threads:[~2014-04-25 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 13:40 [PATCH] Staging: octeon-usb: fixed a macro coding style issue Nicolas Del Piano
2014-04-25 13:42 ` Levente Kurusa [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-25 13:48 Nicolas Del Piano
2014-04-25 14:21 ` Greg KH
2014-04-25 15:58 ` David Daney
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=535A664B.3000805@linux.com \
--to=levex@linux.com \
--cc=aaro.koskinen@iki.fi \
--cc=david.daney@cavium.com \
--cc=devel@driverdev.osuosl.org \
--cc=devendra.aaru@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndel314@gmail.com \
--cc=raluca.oncioiu91@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox