diff options
author | 2024-04-27 22:36:02 +0200 | |
---|---|---|
committer | 2024-05-06 00:56:53 +0200 | |
commit | 4259964b4a5299cb4fb9f5e06dccafb2ae05cb20 (patch) | |
tree | 3c652ee18818329b6755eb789d323061c6613e14 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | i2c: stm32f7: use 'time_left' variable with wait_for_completion_timeout() (diff) | |
download | wireguard-linux-4259964b4a5299cb4fb9f5e06dccafb2ae05cb20.tar.xz wireguard-linux-4259964b4a5299cb4fb9f5e06dccafb2ae05cb20.zip |
i2c: synquacer: 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.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Acked-by: Ard Biesheuvel <ardb@kernel.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