All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juliana Rodrigues <juliana.orod@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: dgnc: replaced udelay with usleep_range in dgnc_cls.c
Date: Sun, 13 Mar 2016 09:17:38 -0300	[thread overview]
Message-ID: <1457871458.12864.9.camel@gmail.com> (raw)
In-Reply-To: <20160313025732.GB11289@kroah.com>

Em Sáb, 2016-03-12 às 18:57 -0800, Greg KH escreveu:
> On Sat, Mar 12, 2016 at 10:13:23PM -0300, Juliana Rodrigues wrote:
> > 
> > This patch replaces udelay with usleep_range fixing a checkpatch.pl
> > issue:
> > 
> > CHECK: usleep_range is preferred over udelay; see
> > Documentation/timers/timers-howto.txt
> > +       udelay(10);
> > 
> > Signed-off-by: Juliana Rodrigues <juliana.orod@gmail.com>
> > ---
> >  drivers/staging/dgnc/dgnc_cls.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/staging/dgnc/dgnc_cls.c
> > b/drivers/staging/dgnc/dgnc_cls.c
> > index 72f0aaa..51db98b 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(10000, 11000);
> How do you know this range is ok?

Probably it isnt. I thought that usleep_range were 
in microseconds while udelay in miliseconds. I'll 
make a patch to fix this. 

Thanks, Greg. :)
> 


      reply	other threads:[~2016-03-13 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13  1:13 [PATCH] staging: dgnc: replaced udelay with usleep_range in dgnc_cls.c Juliana Rodrigues
2016-03-13  2:57 ` [Outreachy kernel] " Greg KH
2016-03-13 12:17   ` Juliana Rodrigues [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=1457871458.12864.9.camel@gmail.com \
    --to=juliana.orod@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.