summaryrefslogtreecommitdiffstats
path: root/drivers/iio/dac
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2024-04-29 13:33:11 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2024-04-29 21:06:18 +0100
commit8d0c93761606ffc97af0cd00901579c5972017ca (patch)
tree98e44844595a54ff91e1b58e5bacccf97d398768 /drivers/iio/dac
parentb0329b3c7ecaaa9a7ebc9fa2c5cdf53fad17ddc9 (diff)
downloadlinux-stable-8d0c93761606ffc97af0cd00901579c5972017ca.tar.gz
linux-stable-8d0c93761606ffc97af0cd00901579c5972017ca.tar.bz2
linux-stable-8d0c93761606ffc97af0cd00901579c5972017ca.zip
iio: pressure: zpa2326: 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-9-wsa+renesas@sang-engineering.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/dac')
0 files changed, 0 insertions, 0 deletions