diff options
| author | Wolfram Sang <[email protected]> | 2024-04-29 13:33:10 +0200 |
|---|---|---|
| committer | Jonathan Cameron <[email protected]> | 2024-04-29 21:06:18 +0100 |
| commit | b0329b3c7ecaaa9a7ebc9fa2c5cdf53fad17ddc9 (patch) | |
| tree | 8cb803832afb7d2cad0687d4e0c5ec302b35c521 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 2f62fd78a14500973d757acb2ebf1b831f708efb (diff) | |
iio: adc: twl6030-gpadc: use 'time_left' variable with wait_for_completion_interruptible_timeout()
There is a confusing pattern in the kernel to use a variable named 'timeout' to
store the result of wait_for_completion_interruptible_timeout() causing patterns like:
timeout = wait_for_completion_interruptible_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 <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jonathan Cameron <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions