staging: rtl8723bs: replace msleep with usleep_range
PATCH 1/1 staging: rtl8723bs: replace msleep with usleep_range
checkpatch.pl warns that msleep < 20ms can sleep for up to 20ms.
This patch replaces msleep(10) with usleep_range(10000, 11000) to improve timer precision and allow the scheduler to coalesce interrupts.
--- drivers/staging/rtl8723bs/core/rtw_cmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/rtl8723bs/core/rtw_cmd.c +1 -1
@@ -214,7 +214,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);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerQuoted 26 lines · Miguel Angel De la Vega Rodriguez
checkpatch.pl warns that msleep < 20ms can sleep for up to 20ms.
This patch replaces msleep(10) with
usleep_range(10000, 11000)to improve timer precision and allow the scheduler to coalesce interrupts.Signed-off-by Miguel Angel De la Vega Rodriguez <[email protected]>--- drivers/staging/rtl8723bs/core/rtw_cmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/staging/rtl8723bs/core/rtw_cmd.c +1
-1@@ -214,7 +214,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);Signature · 1 line
2.53.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, and is identical to ones that have been 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