From: "Moritz C. Weber" <mo.c.weber@gmail.com>
To: marvin24@gmx.de
Cc: ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
"Moritz C. Weber" <mo.c.weber@gmail.com>
Subject: [PATCH] Staging: nvec: nvec: fixed two usleep_range is preferred over udelay warnings
Date: Mon, 12 Feb 2024 14:36:45 +0100 [thread overview]
Message-ID: <20240212133645.1836-1-mo.c.weber@gmail.com> (raw)
Fixed a code style issue raised by checkpatch.
---
drivers/staging/nvec/nvec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index 2823cacde..18c5471d5 100644
--- a/drivers/staging/nvec/nvec.c
+++ b/drivers/staging/nvec/nvec.c
@@ -627,7 +627,7 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
break;
case 2: /* first byte after command */
if (status == (I2C_SL_IRQ | RNW | RCVD)) {
- udelay(33);
+ usleep_range(32, 33);
if (nvec->rx->data[0] != 0x01) {
dev_err(nvec->dev,
"Read without prior read command\n");
@@ -714,7 +714,7 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
* We experience less incomplete messages with this delay than without
* it, but we don't know why. Help is appreciated.
*/
- udelay(100);
+ usleep_range(99, 100);
return IRQ_HANDLED;
}
--
2.30.2
next reply other threads:[~2024-02-12 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:36 Moritz C. Weber [this message]
2024-02-12 13:55 ` [PATCH] Staging: nvec: nvec: fixed two usleep_range is preferred over udelay warnings Dan Carpenter
2024-02-12 14:21 ` Nam Cao
2024-02-16 11:53 ` Thierry Reding
2024-02-18 17:42 ` Marc Dietrich
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=20240212133645.1836-1-mo.c.weber@gmail.com \
--to=mo.c.weber@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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