[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240620115022.24409-1-wsa+renesas@sang-engineering.com>
Date: Thu, 20 Jun 2024 13:50:20 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: linux-kernel@...r.kernel.org
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-arm-kernel@...ts.infradead.org,
linux-fpga@...r.kernel.org,
Michal Simek <michal.simek@....com>,
Moritz Fischer <mdf@...nel.org>,
Wu Hao <hao.wu@...el.com>,
Xu Yilun <yilun.xu@...el.com>
Subject: [PATCH v2 0/2] fpga: 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.
Changes since v1 are stated per patch. Summary: I addressed review
comments and added acks.
Wolfram Sang (2):
fpga: socfpga: use 'time_left' variable with wait_for_completion*()
fpga: zynq-fpga: use 'time_left' variable with
wait_for_completion_timeout()
drivers/fpga/socfpga.c | 7 ++++---
drivers/fpga/zynq-fpga.c | 8 ++++----
2 files changed, 8 insertions(+), 7 deletions(-)
--
2.43.0
Powered by blists - more mailing lists