diff options
author | 2024-04-30 13:41:39 +0200 | |
---|---|---|
committer | 2024-04-30 23:57:31 +0900 | |
commit | 83a3f1ba60d6e2f73c9dd2627a8ce41867dbc46b (patch) | |
tree | a095bb12ea144df789e0bfdfca2d6a718050ed4b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | spi: sun4i: use 'time_left' variable with wait_for_completion_timeout() (diff) | |
download | wireguard-linux-83a3f1ba60d6e2f73c9dd2627a8ce41867dbc46b.tar.xz wireguard-linux-83a3f1ba60d6e2f73c9dd2627a8ce41867dbc46b.zip |
spi: sun6i: 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: Jernej Skrabec <jernej.skrabec@gmail.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Link: https://lore.kernel.org/r/20240430114142.28551-8-wsa+renesas@sang-engineering.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions