diff options
author | Ingo Molnar <[email protected]> | 2011-03-15 20:51:09 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2011-03-15 20:51:09 +0100 |
commit | 5e814dd597c42daeb8d2a276e64a6ec986ad0e2a (patch) | |
tree | e06a7c18e840745869ffa72d568d4c125c7e3fb4 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 137ee20ddd10fdc20600c389fe63edab0c39cb1a (diff) |
perf probe: Clean up probe_point_lazy_walker() return value
Newer compilers (gcc 4.6) complains about:
return ret < 0 ?: 0;
For the following reason:
util/probe-finder.c: In function ‘probe_point_lazy_walker’:
util/probe-finder.c:1331:18: error: the omitted middle operand in ?: will always be ‘true’, suggest explicit middle operand [-Werror=parentheses]
And indeed the return value is a somewhat obscure (but correct) value
of 'true', so return 'ret' instead - this is cleaner and unconfuses
GCC as well.
Cc: Arnaldo Carvalho de Melo <[email protected]>
Cc: Masami Hiramatsu <[email protected]>
Cc: Frederic Weisbecker <[email protected]>
Cc: Masami Hiramatsu <[email protected]>
Cc: Peter Zijlstra <[email protected]>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions