[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240430115438.29134-1-wsa+renesas@sang-engineering.com>
Date: Tue, 30 Apr 2024 13:54:33 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: alsa-devel@...a-project.org
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
Jaroslav Kysela <perex@...ex.cz>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org,
Mark Brown <broonie@...nel.org>,
patches@...nsource.cirrus.com,
Takashi Iwai <tiwai@...e.com>
Subject: [PATCH 0/4] ASoC: use 'time_left' instead of 'timeout' with wait_for_*() functions
There is a confusing pattern in the kernel to use a variable named 'timeout' to
store the result of wait_for_*() 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
(some parts may still be WIP):
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):
ASoC: codecs: wm8962: use 'time_left' variable with
wait_for_completion_timeout()
ASoC: codecs: wm8993: use 'time_left' variable with
wait_for_completion_timeout()
ASoC: codecs: wm8994: use 'time_left' variable with
wait_for_completion_timeout()
ASoC: codecs: wm8996: use 'time_left' variable with
wait_for_completion_timeout()
sound/soc/codecs/wm8962.c | 12 ++++++------
sound/soc/codecs/wm8993.c | 12 ++++++------
sound/soc/codecs/wm8994.c | 8 ++++----
sound/soc/codecs/wm8996.c | 14 +++++++-------
4 files changed, 23 insertions(+), 23 deletions(-)
--
2.43.0
Powered by blists - more mailing lists