misc: apds990x: use 'time_left' variable with wait_event_interruptible_timeout()

There is a confusing pattern in the kernel to use a variable named 'timeout' to
store the result of wait_event_interruptible_timeout() causing patterns like:

	timeout = wait_event_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/20240604212240.4529-2-wsa+renesas@sang-engineering.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/misc/apds990x.c b/drivers/misc/apds990x.c
index 92b92be91d6021a621220ebcd0681365633e17aa..5fb29ebbb4222d83768878f9c3e6bb286ccaca44 100644 (file)
--- a/drivers/misc/apds990x.c
+++ b/drivers/misc/apds990x.c
@@ -625,15 +625,15 @@ static ssize_t apds990x_lux_show(struct device *dev,
        struct apds990x_chip *chip = dev_get_drvdata(dev);
        ssize_t ret;
        u32 result;
-       long timeout;
+       long time_left;
 
        if (pm_runtime_suspended(dev))
                return -EIO;
 
-       timeout = wait_event_interruptible_timeout(chip->wait,
-                                               !chip->lux_wait_fresh_res,
-                                               msecs_to_jiffies(APDS_TIMEOUT));
-       if (!timeout)
+       time_left = wait_event_interruptible_timeout(chip->wait,
+                                                    !chip->lux_wait_fresh_res,
+                                                    msecs_to_jiffies(APDS_TIMEOUT));
+       if (!time_left)
                return -EIO;
 
        mutex_lock(&chip->mutex);