Prev: omap3: make coresight register save across OFF modes a sysfs option
Next: make-3.82 and built in firmware
From: Namhyung Kim on 6 Aug 2010 08:50 percpu data has no special meaning in case of !CONFIG_SMP. This removes lots of sparse warnings. Signed-off-by: Namhyung Kim <namhyung(a)gmail.com> diff --git a/include/linux/compiler.h b/include/linux/compiler.h index a5a472b..8dfd41d 100644 --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -15,7 +15,11 @@ # define __acquire(x) __context__(x,1) # define __release(x) __context__(x,-1) # define __cond_lock(x,c) ((c) ? ({ __acquire(x); 1; }) : 0) -# define __percpu __attribute__((noderef, address_space(3))) +# ifdef CONFIG_SMP +# define __percpu __attribute__((noderef, address_space(3))) +# else +# define __percpu +# endif extern void __chk_user_ptr(const volatile void __user *); extern void __chk_io_ptr(const volatile void __iomem *); #else -- 1.7.0.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |