]> git.karo-electronics.de Git - karo-tx-linux.git/commit
debugobjects: Fix selftest for static warnings
authorStephen Boyd <sboyd@codeaurora.org>
Fri, 16 Dec 2011 04:49:36 +0000 (15:49 +1100)
committerStephen Rothwell <sfr@canb.auug.org.au>
Mon, 19 Dec 2011 07:19:19 +0000 (18:19 +1100)
commit74c1541ae959e872fd1a97d8681a239f19828426
treea9bffdc0d31bc50bc887966817a58d0443985b40
parent0edc53beda0becaf35295ec835cc1256d66faf81
debugobjects: Fix selftest for static warnings

debugobjects is now printing a warning when a fixup for a NOTAVAILABLE
object is run.  This causes the selftest to fail like:

[    0.000000] ODEBUG: selftest warnings failed 4 != 5

We could just increase the number of warnings that the selftest is
expecting to see because that is actually what has changed.  But, it turns
out that fixup_activate() was written with inverted logic and thus a fixup
for a static object returned 1 indicating the object had been fixed, and 0
otherwise.  Fix the logic to be correct and update the counts to reflect
that nothing needed fixing for a static object.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Reported-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
lib/debugobjects.c