From: Greg KH <gregkh@linuxfoundation.org>
To: AyushMukkanwar <ayushmukkanwar@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
ethantidmore06@gmail.com, azpijr@gmail.com,
dan.carpenter@linaro.org
Subject: Re: [PATCH] staging: rtl8723bs: replace msleep(1) with fsleep(1000)
Date: Tue, 31 Mar 2026 10:35:39 +0200 [thread overview]
Message-ID: <2026033135-strangle-wobbly-1957@gregkh> (raw)
In-Reply-To: <20260320180257.40243-1-ayushmukkanwar@gmail.com>
On Fri, Mar 20, 2026 at 11:32:57PM +0530, AyushMukkanwar wrote:
> checkpatch.pl flagged that msleep() is inaccurate for short durations
> under 20ms.
>
> Replace msleep(1) with fsleep(1000) to resolve the warning and align
> with modern kernel timer API standards.
>
> Signed-off-by: AyushMukkanwar <ayushmukkanwar@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_pwrctrl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_pwrctrl.c b/drivers/staging/rtl8723bs/core/rtw_pwrctrl.c
> index f074ea6e0f38..32a5e26bf6bc 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_pwrctrl.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_pwrctrl.c
> @@ -414,7 +414,7 @@ s32 LPS_RF_ON_check(struct adapter *padapter, u32 delay_ms)
> err = -1;
> break;
> }
> - msleep(1);
> + fsleep(1000);
> }
>
> return err;
> @@ -567,7 +567,7 @@ void LPS_Leave_check(struct adapter *padapter)
> if (jiffies_to_msecs(jiffies - start_time) > 100)
> break;
>
> - msleep(1);
> + fsleep(1000);
> }
> }
>
> --
> 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 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
prev parent reply other threads:[~2026-03-31 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 18:02 [PATCH] staging: rtl8723bs: replace msleep(1) with fsleep(1000) AyushMukkanwar
2026-03-31 8:35 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026033135-strangle-wobbly-1957@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ayushmukkanwar@gmail.com \
--cc=azpijr@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=ethantidmore06@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox