summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2024-04-29 14:33:07 +0300
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2024-04-29 23:06:18 +0300
commit1fa9d4a0a4ad6ff98f4d96e98161dcd4e4b7e039 (patch)
tree5f15c62e8678d2711ef2b903a25aee0f3fd8ae89 /tools/perf/scripts/python/export-to-sqlite.py
parent265b81bb7578d5c30866932cab5acde5a9fa0df0 (diff)
downloadlinux-1fa9d4a0a4ad6ff98f4d96e98161dcd4e4b7e039.tar.xz
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 <wsa+renesas@sang-engineering.com> Link: https://lore.kernel.org/r/20240429113313.68359-5-wsa+renesas@sang-engineering.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions