From: Johannes Berg <johannes@sipsolutions.net>
To: ZHAO Gang <gamerh2o@gmail.com>
Cc: "Stefano Brivio" <stefano.brivio@polimi.it>,
"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 <stable@vger.kernel.org>
Subject: [PATCH v3 1/2] b43: fix the wrong assignment of status.freq in b43_rx()
Date: Fri, 17 Jan 2014 16:29:03 +0100 [thread overview]
Message-ID: <1389972543.10404.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <b28b37da08e43e0f459c5094ed210649ab1f7090.1389970392.git.gamerh2o@gmail.com> (sfid-20140117_161955_063280_BEA8D929)
On Fri, 2014-01-17 at 23:19 +0800, ZHAO Gang wrote:
> Use the right function to update status.freq. The wrong frequency
> value can cause problem that bss info can't be updated when it
> should be.
>
> This bug is introduced by commit 8318d78a44d49ac1edf2bdec7299de3617c4232e
> "cfg80211 API for channels/bitrates, mac80211 and driver conversion".
>
> Cc: Stable <stable@vger.kernel.org>
> Signed-off-by: ZHAO Gang <gamerh2o@gmail.com>
> ---
> v3: change commit log
> suggested by Luca Coelho, Rafa? Mi?ecki and Jonas Gorski
>
> I'm not very familiar with wireless subsystem yet. If commit message needs
> more changes, feel free to point it out.
In general, you should also put a Fixes: pseudo-header (with 12-digit
commit ID and commit subject) into such commits, so this would be:
Cc: stable at vger.kernel.org
Fixes: 8318d78a44d4 ("cfg80211 API for channels/bitrates, mac80211 and driver conversion")
Signed-off-by: ...
Thanks for fixing this!
johannes
prev parent reply other threads:[~2014-01-17 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 15:19 [PATCH v3 1/2] b43: fix the wrong assignment of status.freq in b43_rx() ZHAO Gang
2014-01-17 15:19 ` [PATCH v3 2/2] b43: use kernel api to replace b43 specific helper function ZHAO Gang
2014-01-17 15:29 ` Johannes Berg [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=1389972543.10404.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=b43-dev@lists.infradead.org \
--cc=gamerh2o@gmail.com \
--cc=jogo@openwrt.org \
--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).