From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "AyushMukkanwar" <ayushmukkanwar@gmail.com>,
<gregkh@linuxfoundation.org>
Cc: <s9430939@naver.com>, <architanant5@gmail.com>,
<andriy.shevchenko@intel.com>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: Replace msleep with usleep_range
Date: Thu, 19 Mar 2026 15:23:16 -0500 [thread overview]
Message-ID: <DH71FH1KOEKG.7DDYS7US7ZP5@gmail.com> (raw)
In-Reply-To: <20260319195437.53068-1-ayushmukkanwar@gmail.com>
On Thu Mar 19, 2026 at 2:54 PM CDT, AyushMukkanwar wrote:
> The checkpatch.pl script flagged a warning regarding the use of
> msleep() for less than 20ms. msleep() relies on jiffies and can
> be inaccurate for short durations, leading to inefficient delays.
>
> Replace msleep(10) with usleep_range(10000, 12000) to allow for
> timer coalescing. This gives the kernel scheduler a 2ms window
> to group wakeups, improving overall system power efficiency
> while maintaining the required 10ms minimum delay.
>
> Signed-off-by: AyushMukkanwar <ayushmukkanwar@gmail.com>
> ---
Greg has already NAKed this change.
Thanks,
ET
next prev parent reply other threads:[~2026-03-19 20:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 19:54 [PATCH] staging: rtl8723bs: Replace msleep with usleep_range AyushMukkanwar
2026-03-19 20:23 ` Ethan Tidmore [this message]
2026-03-20 7:42 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2026-03-14 5:11 [PATCH] staging: rtl8723bs: replace " Marcos Andrade
2026-03-14 20:56 ` Ethan Tidmore
2026-03-09 0:40 sluisr
2026-03-09 13:33 ` Bryant Boatright
2026-03-09 16:01 ` Greg KH
2026-02-14 17:31 Ofek Almog
2026-02-14 18:11 ` Ethan Tidmore
2026-02-14 18:24 ` Andy Shevchenko
2026-02-14 19:23 ` Ofek Almog
2026-02-15 6:52 ` Greg KH
2026-02-10 5:58 Vo Thanh Cong
2026-02-10 6:37 ` Greg Kroah-Hartman
2026-02-09 12:07 Ethan Lam
2026-02-09 12:35 ` Greg KH
2026-02-08 12:15 Miguel Angel De la Vega Rodriguez
2026-02-08 14:35 ` Greg Kroah-Hartman
2026-01-10 20:44 Işıkhan IŞIK
2026-01-11 12:49 ` Greg KH
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=DH71FH1KOEKG.7DDYS7US7ZP5@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=architanant5@gmail.com \
--cc=ayushmukkanwar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=s9430939@naver.com \
/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