[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c4c9f013-3cff-47dd-9adb-76b30925d8c7@gmx.net>
Date: Thu, 20 Jun 2024 22:42:05 +0200
From: Stefan Wahren <wahrenst@....net>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>, Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>, linux-staging@...ts.linux.dev,
linux-rpi-kernel@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] staging: vc04_services: use 'time_left' variable with
wait_for_completion_timeout()
Am 20.06.24 um 20:25 schrieb Wolfram Sang:
> There is a confusing pattern in the kernel to use a variable named
> 'timeout' to store the result of wait_for_completion_timeout() 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 self explaining.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
Reviewed-by: Stefan Wahren <wahrenst@....net>
Thanks
Powered by blists - more mailing lists