From: Matthew Wilcox <willy@infradead.org>
To: Gideon Adjei <gideonadjei.dev@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Abdun Nihaal <abdun.nihaal@gmail.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Jianglei Nie <niejianglei2021@163.com>,
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: Change udelay() to usleep_range()
Date: Tue, 13 Jan 2026 17:53:52 +0000 [thread overview]
Message-ID: <aWaGsGhS-nNrDjDA@casper.infradead.org> (raw)
In-Reply-To: <20260113172756.14744-1-gideonadjei.dev@gmail.com>
On Tue, Jan 13, 2026 at 09:27:56AM -0800, Gideon Adjei wrote:
> Replace udelay() calls >= 100us with usleep_range() to avoid busy-waiting.
> This allows the scheduler to run other tasks while waiting.
Your commit message omits how you know it's safe to sleep in these
situations. Are we holding a spinlock or being called in interrupt
context, for example?
prev parent reply other threads:[~2026-01-13 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:27 [PATCH] staging: fbtft: Change udelay() to usleep_range() Gideon Adjei
2026-01-13 17:53 ` Matthew Wilcox [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=aWaGsGhS-nNrDjDA@casper.infradead.org \
--to=willy@infradead.org \
--cc=abdun.nihaal@gmail.com \
--cc=andy@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gideonadjei.dev@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=niejianglei2021@163.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