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:02 +0100
committerGreg Kroah-Hartman <[email protected]>2024-09-03 12:10:38 +0200
commit9c6fd5fc98d21cdd2027f702463946b327ff22ee (patch)
tree6c4142a64c3b4e1502e98155287a4421eab26747 /tools/perf/util/scripting-engines/trace-event-python.c
parenteee75a3a3ba35fdc7723465d49314976b020a509 (diff)
slimbus: qcom-ctrl: 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