From: Greg KH <gregkh@linuxfoundation.org>
To: Aybuke Ozdemir <aybuke.147@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: dgnc: usleep_range is preferred over udelay
Date: Thu, 11 Feb 2016 19:51:38 -0800 [thread overview]
Message-ID: <20160212035138.GA30306@kroah.com> (raw)
In-Reply-To: <1455196470-4026-1-git-send-email-aybuke.147@gmail.com>
On Thu, Feb 11, 2016 at 03:14:30PM +0200, Aybuke Ozdemir wrote:
> This patch fixes the issue:
>
> CHECK: usleep_range is preferred over udelay; see
> Documentation/timers/timers-howto.txt
>
> Signed-off-by: Aybuke Ozdemir <aybuke.147@gmail.com>
> ---
> drivers/staging/dgnc/dgnc_cls.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/dgnc/dgnc_cls.c b/drivers/staging/dgnc/dgnc_cls.c
> index 72f0aaa..ce1471b 100644
> --- a/drivers/staging/dgnc/dgnc_cls.c
> +++ b/drivers/staging/dgnc/dgnc_cls.c
> @@ -956,7 +956,7 @@ static void cls_flush_uart_read(struct channel_t *ch)
> * Presumably, this is a bug in this UART.
> */
>
> - udelay(10);
> + usleep_range(10, 100);
As Tejun pointed out, this isn't ok, you can just ignore that checkpatch
warning. Maybe we don't want to sleep for 100, are you sure about that?
Without the hardware to test with, we don't want to touch stuff like
this, sorry.
greg k-h
prev parent reply other threads:[~2016-02-12 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 13:14 [PATCH] staging: dgnc: usleep_range is preferred over udelay Aybuke Ozdemir
2016-02-11 15:50 ` [Outreachy kernel] " Tejun Heo
2016-02-11 15:53 ` Julia Lawall
2016-02-11 15:58 ` Tejun Heo
2016-02-12 3:51 ` Greg KH [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=20160212035138.GA30306@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aybuke.147@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.