tools/lib/lockdep: Fix 'unused value' warnings
liblockdep defines various macros that may expand to an expression with no effect, while the in-kernel definition does have an effect. This results in warnings from gcc when -Wunused-value is enabled, and is is enabled by -Wall. Fix this by introducing trivial functions, as function return values are generally allowed to be ignored. Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: a.p.zijlstra@chello.nl Link: http://lkml.kernel.org/r/20170525130005.5947-6-alexander.levin@verizon.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
committed by
Ingo Molnar
parent
db8f7796c4
commit
bb7ea2a9af
@@ -22,10 +22,16 @@
|
||||
_max1 > _max2 ? _max1 : _max2; })
|
||||
|
||||
#define BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
|
||||
#define WARN_ON(x) (x)
|
||||
#define WARN_ON_ONCE(x) (x)
|
||||
|
||||
static inline int lockdep_warn(int condition)
|
||||
{
|
||||
return condition;
|
||||
}
|
||||
#define WARN_ON(x) lockdep_warn(x)
|
||||
#define WARN_ON_ONCE(x) WARN_ON(x)
|
||||
#define WARN(x, y...) WARN_ON(x)
|
||||
|
||||
#define likely(x) (x)
|
||||
#define WARN(x, y...) (x)
|
||||
#define uninitialized_var(x) x
|
||||
#define __init
|
||||
#define noinline
|
||||
|
||||
Reference in New Issue
Block a user