Phil Carmody 497888cf69 treewide: fix potentially dangerous trailing ';' in #defined values/expressions ... All these are instances of #define NAME value; or #define NAME(params_opt) value; These of course fail to build when used in contexts like if(foo $OP NAME) while(bar $OP NAME) and may silently generate the wrong code in contexts such as foo = NAME + 1; /* foo = value; + 1; */ bar = NAME - 1; /* bar = value; - 1; */ baz = NAME & quux; /* baz = value; & quux; */ Reported on comp.lang.c, Message-ID: <ab0d55fe-25e5-482b-811e-c475aa6065c3@c29g2000yqd.googlegroups.com> Initial analysis of the dangers provided by Keith Thompson in that thread. There are many more instances of more complicated macros having unnecessary trailing semicolons, but this pile seems to be all of the cases of simple values suffering from the problem. (Thus things that are likely to be found in one of the contexts above, more complicated ones aren't.) Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>		2011-07-21 14:10:00 +02:00
..
timer
asm-offsets.c
entry.S
gpio.c
h8300_ksyms.c
init_task.c
irq.c
Makefile
module.c
process.c
ptrace.c
setup.c	treewide: fix potentially dangerous trailing ';' in #defined values/expressions	2011-07-21 14:10:00 +02:00
signal.c
sys_h8300.c
syscalls.S	ns: Wire up the setns system call	2011-05-28 10:48:39 -07:00
time.c
traps.c
vmlinux.lds.S