diff options
author | 2024-04-27 22:36:01 +0200 | |
---|---|---|
committer | 2024-05-06 00:56:52 +0200 | |
commit | 197264d377b875dfc5be3c12125bc35fc3643204 (patch) | |
tree | 79cae23c1f92b34905fcafdd9c12496c793a7ec8 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | i2c: stm32f4: use 'time_left' variable with wait_for_completion_timeout() (diff) | |
download | wireguard-linux-197264d377b875dfc5be3c12125bc35fc3643204.tar.xz wireguard-linux-197264d377b875dfc5be3c12125bc35fc3643204.zip |
i2c: stm32f7: 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>
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