diff options
| author | Wolfram Sang <[email protected]> | 2024-04-29 13:33:09 +0200 |
|---|---|---|
| committer | Jonathan Cameron <[email protected]> | 2024-04-29 21:06:18 +0100 |
| commit | 2f62fd78a14500973d757acb2ebf1b831f708efb (patch) | |
| tree | 1bae00612bc1d23bf9239d7c2b3835e2f388d877 /tools/perf/scripts/python/bin | |
| parent | 3cd191fce83726c39b74515820b3ec8f23e1768b (diff) | |
iio: adc: stm32-dfsdm-adc: 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')
0 files changed, 0 insertions, 0 deletions