[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYmbp4VL7X9QTx9P@smile.fi.intel.com>
Date: Mon, 9 Feb 2026 10:32:39 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Neel Bullywon <neelb2403@...il.com>
Cc: apw@...onical.com, joe@...ches.com, dwaipayanray1@...il.com,
lukas.bulwahn@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] checkpatch: suggest fsleep() for short msleep() calls
On Sun, Feb 08, 2026 at 10:59:35AM -0500, Neel Bullywon wrote:
> Update the MSLEEP warning to suggest fsleep() as a duration based
> sleep API. fsleep() autoselects the best sleep mechanism (udelay,
> usleep_range, or msleep) based on the requested duration, making
> it the preferred replacement for short msleep() calls.
Hmm... My understanding was that the warning itself has a mention of
usleep_range(). Looking at the patch I think the current wording is
okay, but it may be expanded to suggest fsleep().
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists