From: Dan Carpenter <dan.carpenter@linaro.org>
To: Uros Milojkovic <uroshm@gmail.com>
Cc: linux-kernel@vger.kernel.org, marvin24@gmx.de,
p.zabel@pengutronix.de, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: nvec: udelay to usleep_range
Date: Mon, 26 Jun 2023 16:01:05 +0300 [thread overview]
Message-ID: <b7319d00-d8db-4e8b-9143-7926f8a34fbe@kadam.mountain> (raw)
In-Reply-To: <CAP=xWk6GvVQxzTJ6jS2pQ9dKvgoFFHc=m4yMma101MGKgdcm5A@mail.gmail.com>
On Sun, Jun 25, 2023 at 02:55:35PM -0400, Uros Milojkovic wrote:
> Checkpatch pl alerts that usleep_range is preferred to udelay. The
> change is made.
> Signed-off-by: umilojkovic <uroshm@gmail.com>
> ---
> 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 2823cacde130..8bb3b691d1f5 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(33, 200);
These kind of patches are only allowed if you have actually tested it
on real hardware.
> if (nvec->rx->data[0] != 0x01) {
> dev_err(nvec->dev,
> "Read without prior read command\n");
regards,
dan carpenter
next prev parent reply other threads:[~2023-06-26 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 18:55 [PATCH] staging: nvec: udelay to usleep_range Uros Milojkovic
2023-06-26 6:09 ` Greg KH
2023-06-26 13:01 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-25 18:51 Uros Milojkovic
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=b7319d00-d8db-4e8b-9143-7926f8a34fbe@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=p.zabel@pengutronix.de \
--cc=uroshm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox