diff options
author | 2024-04-27 22:36:03 +0200 | |
---|---|---|
committer | 2024-05-06 00:56:53 +0200 | |
commit | 66aa72ced659c5cf3e14674e04450f92e845a699 (patch) | |
tree | 4f55120603de043aa0c147ab0f7e087ce8351eec /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | i2c: synquacer: use 'time_left' variable with wait_for_completion_timeout() (diff) | |
download | wireguard-linux-66aa72ced659c5cf3e14674e04450f92e845a699.tar.xz wireguard-linux-66aa72ced659c5cf3e14674e04450f92e845a699.zip |
i2c: jz4780: 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 <wsa+renesas@sang-engineering.com>
Acked-by: Paul Cercueil <paul@crapouillou.net>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions