All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: FMDF <fmdefrancesco@gmail.com>
Cc: outreachy-kernel@googlegroups.com, jerome.pouiller@silabs.com
Subject: Re: [PATCH] staging: wfx: Replace udelay() by usleep_range() in bh.c
Date: Mon, 5 Apr 2021 12:17:50 +0200	[thread overview]
Message-ID: <YGrjzt41FM88YvEv@kroah.com> (raw)
In-Reply-To: <CAPj211tmd7AY2-nym6AVOg_kVFKDZzNQBZ7x-kwrFZRaCnfnxw@mail.gmail.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Mon, Apr 05, 2021 at 12:15:17PM +0200, FMDF wrote:
> Thanks for your prompt reply. No, I don't know it for sure. I've just
> read some drivers and found that often the maximum time is about 150%
> of the minimum. I assumed (wrongly) that it was safe.
> 
> Can I leave usleep_range() with 200 usec for min and max time, as it
> was with udelay(), and let the maintainer to take care of the numbers?

I would just leave it as-is for now, no need to change it.

thanks,

greg k-h


      reply	other threads:[~2021-04-05 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05  9:52 [PATCH] staging: wfx: Replace udelay() by usleep_range() in bh.c Fabio M. De Francesco
2021-04-05 10:03 ` Greg KH
2021-04-05 10:15   ` FMDF
2021-04-05 10:17     ` 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=YGrjzt41FM88YvEv@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=jerome.pouiller@silabs.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.