From: Larry Finger <Larry.Finger@lwfinger.net>
To: ZHAO Gang <gamerh2o@gmail.com>,
Stefano Brivio <stefano.brivio@polimi.it>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Jonas Gorski" <jogo@openwrt.org>, "Luca Coelho" <luca@coelho.fi>,
"Rafał Miłecki" <zajec5@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v4 1/2] b43: fix the wrong assignment of status.freq in b43_rx()
Date: Fri, 17 Jan 2014 16:18:07 -0600 [thread overview]
Message-ID: <52D9AC1F.6090002@lwfinger.net> (raw)
In-Reply-To: <d4d1340a176aee1e58ffe80e83ddc3394f2829e3.1389975095.git.gamerh2o@gmail.com>
On 01/17/2014 10:17 AM, ZHAO Gang wrote:
> Use the right function to update frequency value.
>
> If rx skb is probe response or beacon, the wrong frequency value can
> cause problem that bss info can't be updated when it should be.
>
> Cc: <stable@vger.kernel.org>
> Fixes: 8318d78a44d4 ("cfg80211 API for channels/bitrates, mac80211
> and driver conversion")
> Signed-off-by: ZHAO Gang <gamerh2o@gmail.com>
> ---
This patch seems to fix a problem that caused scanning under NetworkManager to
fail. The symptom was that no available networks were seen in the NM applet
after a connection was made. Now the available AP list remains populated.
Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
Larry
next prev parent reply other threads:[~2014-01-17 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 16:17 [PATCH v4 1/2] b43: fix the wrong assignment of status.freq in b43_rx() ZHAO Gang
2014-01-17 16:17 ` [PATCH v4 2/2] b43: use kernel api to replace b43 specific helper function ZHAO Gang
2014-01-17 22:18 ` Larry Finger [this message]
2014-01-26 14:35 ` [PATCH v4 1/2] b43: fix the wrong assignment of status.freq in b43_rx() Rafał Miłecki
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=52D9AC1F.6090002@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=gamerh2o@gmail.com \
--cc=jogo@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luca@coelho.fi \
--cc=stable@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
--cc=zajec5@gmail.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 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).