[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240604212240.4529-1-wsa+renesas@sang-engineering.com>
Date: Tue, 4 Jun 2024 23:22:35 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: linux-kernel@...r.kernel.org
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
Alex Dubov <oakad@...oo.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: [PATCH 0/4] misc: use 'time_left' instead of 'timeout' with wait_*() functions
There is a confusing pattern in the kernel to use a variable named 'timeout' to
store the result of wait_*() functions causing patterns like:
timeout = wait_for_completion_timeout(...)
if (!timeout) return -ETIMEDOUT;
with all kinds of permutations. Use 'time_left' as a variable to make the code
obvious and self explaining.
This is part of a tree-wide series. The rest of the patches can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/time_left
Because these patches are generated, I audit them before sending. This is why I
will send series step by step. Build bot is happy with these patches, though.
No functional changes intended.
Wolfram Sang (4):
misc: apds990x: use 'time_left' variable with
wait_event_interruptible_timeout()
misc: bh1770glc: use 'time_left' variable with
wait_event_interruptible_timeout()
misc: tifm: use 'time_left' variable with
wait_for_completion_timeout()
misc: ti-st: st_kim: use 'time_left' variable with
wait_for_completion_interruptible_timeout()
drivers/misc/apds990x.c | 10 +++++-----
drivers/misc/bh1770glc.c | 10 +++++-----
drivers/misc/ti-st/st_kim.c | 8 ++++----
drivers/misc/tifm_7xx1.c | 6 +++---
4 files changed, 17 insertions(+), 17 deletions(-)
--
2.43.0
Powered by blists - more mailing lists