diff options
| author | Wolfram Sang <[email protected]> | 2024-04-29 13:33:07 +0200 |
|---|---|---|
| committer | Jonathan Cameron <[email protected]> | 2024-04-29 21:06:18 +0100 |
| commit | 1fa9d4a0a4ad6ff98f4d96e98161dcd4e4b7e039 (patch) | |
| tree | 5f15c62e8678d2711ef2b903a25aee0f3fd8ae89 /tools/perf/scripts/python/bin | |
| parent | 265b81bb7578d5c30866932cab5acde5a9fa0df0 (diff) | |
iio: adc: intel_mrfld_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