summaryrefslogtreecommitdiff
path: root/drivers/iio/adc/stm32-dfsdm-adc.c
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2024-04-29 13:33:08 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2024-04-29 21:06:18 +0100
commit3cd191fce83726c39b74515820b3ec8f23e1768b (patch)
tree6e2d3a417e9a2964f049332ac9d6aadbb8921bdc /drivers/iio/adc/stm32-dfsdm-adc.c
parent1fa9d4a0a4ad6ff98f4d96e98161dcd4e4b7e039 (diff)
iio: adc: stm32-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 <wsa+renesas@sang-engineering.com> Link: https://lore.kernel.org/r/20240429113313.68359-6-wsa+renesas@sang-engineering.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/adc/stm32-dfsdm-adc.c')
0 files changed, 0 insertions, 0 deletions