Linux kernel staging patches
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Leonardo Araujo <leonardo.aa88@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] Staging: wfx: CHECK: usleep_range is preferred over udelay
Date: Mon, 07 Feb 2022 09:28:13 -0800	[thread overview]
Message-ID: <355c9305d74c666a976b526f3d80ce208c0ec927.camel@perches.com> (raw)
In-Reply-To: <YgFM1HHs7rSqp/0Q@kroah.com>

On Mon, 2022-02-07 at 17:46 +0100, Greg KH wrote:
> On Mon, Feb 07, 2022 at 01:00:51PM -0300, Leonardo Araujo wrote:
> > Fixes the checks reported by checkpatch.pl for usleep_range.
[]
> > diff --git a/drivers/staging/wfx/bh.c b/drivers/staging/wfx/bh.c
[]
> > @@ -312,7 +312,7 @@ void wfx_bh_poll_irq(struct wfx_dev *wdev)
> >  			dev_err(wdev->dev, "time out while polling control register\n");
> >  			return;
> >  		}
> > -		udelay(200);
> > +		usleep_range(200, 200);

range with the same low/high values is pretty useless.

And Leonardo, checkpatch should have warned you about this.
You, as a novice kernel submitter, should always use it on patches
you create before you send them out for review.

> Do you have the hardware to verify that this is the correct fix for
> this?
> 
> You can not just blindly make this type of change here, sorry, otherwise
> we would have done so long ago with a simple search/replace :)

Greg, you keep writing this but treewide search/replace is almost never done.



      reply	other threads:[~2022-02-07 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 16:00 [PATCH] Staging: wfx: CHECK: usleep_range is preferred over udelay Leonardo Araujo
2022-02-07 16:46 ` Greg KH
2022-02-07 17:28   ` Joe Perches [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=355c9305d74c666a976b526f3d80ce208c0ec927.camel@perches.com \
    --to=joe@perches.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=leonardo.aa88@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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