[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878qzlt9aa.fsf@kernel.org>
Date: Tue, 04 Jun 2024 11:13:49 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Ping-Ke Shih <pkshih@...ltek.com>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: [PATCH 5/6] wifi: rtw89: use 'time_left' variable with
wait_for_completion_timeout()
Ping-Ke Shih <pkshih@...ltek.com> writes:
> Wolfram Sang <wsa+renesas@...g-engineering.com> wrote:
>> 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>
>
> Acked-by: Ping-Ke Shih <pkshih@...ltek.com>
BTW Ping, you can also take it directly to your tree if you want. But if you
want me to take the patch, then please assign it to me on patchwork (ie.
change 'Delegate to' to 'kvalo'). My preference is to take it to your
tree, smaller risk of concflicts that way, but up to you.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists