aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorWolfram Sang <[email protected]>2024-09-02 15:10:01 +0100
committerGreg Kroah-Hartman <[email protected]>2024-09-03 12:10:38 +0200
commiteee75a3a3ba35fdc7723465d49314976b020a509 (patch)
tree24b1d3d6eb6c32ec898575f34ce908fa9c9d7b13 /tools/perf/util/scripting-engines/trace-event-python.c
parent59d617dc727e06f97481331722b589715b3b4a87 (diff)
slimbus: messaging: use 'time_left' variable with wait_for_completion_timeout()
There is a confusing pattern in the kernel to use a variable named 'timeout' to store the result of wait_for_completion_timeout() causing patterns like: timeout = wait_for_completion_timeout(...) if (!timeout) return -ETIMEDOUT; with all kinds of permutations. Use 'time_left' as a variable to make the code self explaining. Fix to the proper variable type 'unsigned long' while here. Signed-off-by: Wolfram Sang <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Reviewed-by: Bjorn Andersson <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions