From: Kalle Valo <kvalo@codeaurora.org>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: Larry.Finger@lwfinger.net, kstewart@linuxfoundation.org,
johannes.berg@intel.com, tiwai@suse.de,
gregkh@linuxfoundation.org, colin.king@canonical.com,
andrew.zaborowski@intel.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
b43-dev@lists.infradead.org, Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: Re: [v2] b43: Replace mdelay with usleep_range in b43_radio_2057_init_post
Date: Thu, 11 Jan 2018 19:54:29 +0000 (UTC) [thread overview]
Message-ID: <20180111195429.CDE4660BEA@smtp.codeaurora.org> (raw)
In-Reply-To: <1515462006-6144-1-git-send-email-baijiaju1990@gmail.com>
Jia-Ju Bai <baijiaju1990@gmail.com> wrote:
> b43_radio_2057_init_post is not called in an interrupt handler
> nor holding a spinlock.
> The function mdelay in it can be replaced with usleep_range,
> to reduce busy wait.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
> Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
Patch applied to wireless-drivers-next.git, thanks.
4330b53e9662 b43: Replace mdelay with usleep_range in b43_radio_2057_init_post
--
https://patchwork.kernel.org/patch/10150845/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-01-11 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 1:40 [PATCH v2] b43: Replace mdelay with usleep_range in b43_radio_2057_init_post Jia-Ju Bai
2018-01-09 8:35 ` Greg KH
2018-01-09 8:39 ` Jia-Ju Bai
2018-01-09 9:07 ` Arend van Spriel
2018-01-09 9:47 ` Jia-Ju Bai
2018-01-09 11:11 ` Arend van Spriel
2018-01-09 16:49 ` Larry Finger
[not found] ` <1515462006-6144-1-git-send-email-baijiaju1990-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-11 19:54 ` [v2] " Kalle Valo
2018-01-11 19:54 ` Kalle Valo [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=20180111195429.CDE4660BEA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=andrew.zaborowski@intel.com \
--cc=b43-dev@lists.infradead.org \
--cc=baijiaju1990@gmail.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).