[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2026020944-mummified-scope-4221@gregkh>
Date: Mon, 9 Feb 2026 13:35:56 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ethan Lam <ethanlxkernel@...il.com>
Cc: linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
ignacio.pena87@...il.com, bryant.boatright@...ton.me,
strnad.jj@...il.com, mingo@...nel.org, tglx@...utronix.de
Subject: Re: [PATCH] staging: rtl8723bs: replace msleep with usleep_range
On Mon, Feb 09, 2026 at 08:07:09PM +0800, Ethan Lam wrote:
> checkpatch.pl says that msleep < 20ms can sleep for longer than expected.
> The documentation says we should "Use uslee_range*()
> whenever accuracy of *sleep() is not sufficient)
>
> Replaced msleep(10) with usleep_range(10000, 11000) so the delay
> is more accurate and percise
>
> Signed-off-by: Ethan Lam <ethanlxkernel@...il.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_cmd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_cmd.c b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> index ef2d92b5588a..97c923015279 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> @@ -215,7 +215,7 @@ void _rtw_free_evt_priv(struct evt_priv *pevtpriv)
> {
> _cancel_workitem_sync(&pevtpriv->c2h_wk);
> while (pevtpriv->c2h_wk_alive)
> - msleep(10);
> + usleep_range(10000, 11000);
>
> while (!rtw_cbuf_empty(pevtpriv->c2h_queue)) {
> void *c2h = rtw_cbuf_pop(pevtpriv->c2h_queue);
> --
> 2.43.0
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You sent a patch that has been sent multiple times in the past few
days, and is identical to ones that has been recently rejected.
Please always look at the mailing list traffic to determine if you are
duplicating other people's work.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists