From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: mashikiselby@gmail.com
Cc: Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fb_ra8875: replace udelay with usleep_range
Date: Thu, 16 Jul 2026 21:37:24 +0300 [thread overview]
Message-ID: <alkk5CVmeEY6org0@ashevche-desk.local> (raw)
In-Reply-To: <20260716-staging-testing-v1-1-2ebc0c6bb27a@gmail.com>
On Thu, Jul 16, 2026 at 01:08:33PM +0200, Selby Mashiki via B4 Relay wrote:
> udelay() busy-waits for the specified duration, consuming CPU cycles
> unnecessarily. usleep_range() is preferred for delays that can sleep,
> as it allows the scheduler to run other tasks during the wait.
>
> Replace two instances of udelay(100) with usleep_range(100, 200) to
> use the preferred sleeping delay function.
NAK. Read mailing list archives why.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-16 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 11:08 [PATCH] staging: fbtft: fb_ra8875: replace udelay with usleep_range Selby Mashiki via B4 Relay
2026-07-16 11:08 ` Selby Mashiki
2026-07-16 11:19 ` sashiko-bot
2026-07-16 18:37 ` Andy Shevchenko [this message]
[not found] <20260218174737.86994-1-tomasz.unger.ref@yahoo.pl>
2026-02-18 17:47 ` tomasz.unger
2026-02-19 7:30 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 19:15 Olle Lukowski
2025-10-21 7:37 ` Greg Kroah-Hartman
2025-10-21 8:12 ` Olle Lukowski
2025-10-21 8:50 ` Andy Shevchenko
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=alkk5CVmeEY6org0@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mashikiselby@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.