From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Mahdi Ghorbanian <indigoomega021@gmail.com>
Cc: marvin24@gmx.de, devel@driverdev.osuosl.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
ac100@lists.launchpad.net
Subject: Re: [PATCH 2/2] Staging: nvec: nvec: fixed check style issues
Date: Mon, 17 Dec 2018 09:16:40 +0100 [thread overview]
Message-ID: <20181217081640.GA16368@kroah.com> (raw)
In-Reply-To: <1544979463-10126-1-git-send-email-indigoomega021@gmail.com>
On Sun, Dec 16, 2018 at 08:57:43AM -0800, Amir Mahdi Ghorbanian wrote:
> @@ -626,7 +628,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(0, 33);
Why is this a valid range to sleep for for this device? Have you been
able to verify/test this?
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-17 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 16:57 [PATCH 2/2] Staging: nvec: nvec: fixed check style issues Amir Mahdi Ghorbanian
2018-12-16 17:47 ` Joe Perches
2018-12-17 1:07 ` kbuild test robot
2018-12-17 8:16 ` Greg KH [this message]
2018-12-17 19:48 ` 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=20181217081640.GA16368@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ac100@lists.launchpad.net \
--cc=devel@driverdev.osuosl.org \
--cc=indigoomega021@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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