[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08985c11-3652-4699-81d9-8a6769b061da@broadcom.com>
Date: Mon, 3 Jun 2024 11:42:57 +0200
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-kernel@...r.kernel.org
Cc: Kalle Valo <kvalo@...nel.org>, linux-wireless@...r.kernel.org,
brcm80211@...ts.linux.dev, brcm80211-dev-list.pdl@...adcom.com
Subject: Re: [PATCH 2/6] wifi: brcmfmac: use 'time_left' variable with
wait_event_timeout()
On 6/3/2024 11:15 AM, Wolfram Sang wrote:
> There is a confusing pattern in the kernel to use a variable named 'timeout' to
> store the result of wait_event_timeout() causing patterns like:
>
> timeout = wait_event_timeout(...)
> if (!timeout) return -ETIMEDOUT;
>
> with all kinds of permutations. Use 'time_left' as a variable to make the code
> self explaining.
I feel this type of changes fall into the category of bike-shedding.
People should know how wait_event_timeout() works and then a variable
name does not really matter.
> Fix to the proper variable type 'long' while here.
But it may have useful side-effects to go over the code with fresh look.
Thanks.
Acked-by: Arend van Spriel <arend.vanspriel@...adcom.com>
> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
> ---
> .../wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4219 bytes)
Powered by blists - more mailing lists