diff options
| author | Stephen Boyd <[email protected]> | 2012-03-05 14:59:17 -0800 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2012-03-05 15:49:43 -0800 |
| commit | 9f78ff005a6b6313728247113948450b2adddde8 (patch) | |
| tree | 91bf021b9d2d1a09ae74a39c11275aacaf6082f1 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 9354f1b8e6c55c335d1c4fb10d0ae7a041935240 (diff) | |
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:
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 <[email protected]>
Reported-by: Thomas Gleixner <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions