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>
 
        struct stm32_adc *adc = iio_priv(indio_dev);
        struct device *dev = indio_dev->dev.parent;
        const struct stm32_adc_regspec *regs = adc->cfg->regs;
-       long timeout;
+       long time_left;
        u32 val;
        int ret;
 
 
        adc->cfg->start_conv(indio_dev, false);
 
-       timeout = wait_for_completion_interruptible_timeout(
+       time_left = wait_for_completion_interruptible_timeout(
                                        &adc->completion, STM32_ADC_TIMEOUT);
-       if (timeout == 0) {
+       if (time_left == 0) {
                ret = -ETIMEDOUT;
-       } else if (timeout < 0) {
-               ret = timeout;
+       } else if (time_left < 0) {
+               ret = time_left;
        } else {
                *res = adc->buffer[0];
                ret = IIO_VAL_INT;