Re: [PATCH 3/5] tg3: Enclose macro with complex values in parenthesis

[PATCH 1/5] tg3: use <linux/io.h> and <linux/uaccess.h> instead <asm/io.h> and <asm/uaccess.h> · Javier Martinez Canillas <hidden> · 2011-03-01
[PATCH 1/5] tg3: use usleep_range not msleep for small sleeps · Javier Martinez Canillas <hidden> · 2011-03-01
Re: [PATCH 1/5] tg3: use usleep_range not msleep for small sleeps · David Miller <davem@davemloft.net> · 2011-03-03
Re: [PATCH 1/5] tg3: use usleep_range not msleep for small sleeps · Javier Martinez Canillas <hidden> · 2011-03-03
[PATCH 3/5] tg3: Enclose macro with complex values in parenthesis · Javier Martinez Canillas <hidden> · 2011-03-01
Re: [PATCH 3/5] tg3: Enclose macro with complex values in parenthesis · David Miller <davem@davemloft.net> · 2011-03-03
Re: [PATCH 3/5] tg3: Enclose macro with complex values in parenthesis · Javier Martinez Canillas <hidden> · 2011-03-03
[PATCH 4/5] tg3: Don't use IRQF_SAMPLE_RANDOM · Javier Martinez Canillas <hidden> · 2011-03-01
[PATCH 5/5] tg3: Fix inline keyword usage · Javier Martinez Canillas <hidden> · 2011-03-01

From: Javier Martinez Canillas <hidden>
Date: 2011-03-03 11:55:08
Also in: kernelnewbies

This seems unnecessary, what problem do the current macro definitions
create?

Probably the change is unnecessary, the only value is that it silences
a checkpatch error:

ERROR: Macros with complex values should be enclosed in parenthesis

Sorry for the noise.

-- 
-----------------------------------------
Javier Martínez Canillas
(+34) 682 39 81 69
PhD Student in High Performance Computing
Computer Architecture and Operating System Department (CAOS)
Universitat Autònoma de Barcelona
Barcelona, Spain

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help