From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Emmanuel Grumbach" <egrumbach@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev@lists.infradead.org,
"Aaro Koskinen" <aaro.koskinen@iki.fi>
Subject: [RFC: which stable kernels?] b43: fix frequency reported on G-PHY with /new/ firmware
Date: Thu, 12 Jun 2014 14:43:45 +0200 [thread overview]
Message-ID: <1402577025.8095.16.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <53995A1F.6000405@broadcom.com> (sfid-20140612_094333_618630_0312AC3F)
On Thu, 2014-06-12 at 09:43 +0200, Arend van Spriel wrote:
> On 12-06-14 09:35, Emmanuel Grumbach wrote:
> >> ---
> >> This bug was there for years, however didn't cause any problems. It was
> >> exposed recently by the 3.15 release by the:
> >>
> >> commit 3afc2167f60a327a2c1e1e2600ef209a3c2b75b7
> >> Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> >> Date: Tue Mar 4 16:50:13 2014 +0200
> >>
> >> cfg80211/mac80211: ignore signal if the frame was heard on wrong channel
> >>
> >> Should we mark it for stable for 3.15 only? Or all olders kernels as well?
> >
> > Up to you - my patch is in 3.15 only I think.
>
> Is there any scenario that would expose the worng info. Maybe when using
> monitor mode?
Yeah that'd probably be messed up as well.
johannes
prev parent reply other threads:[~2014-06-12 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 7:28 [RFC: which stable kernels?] b43: fix frequency reported on G-PHY with /new/ firmware Rafał Miłecki
2014-06-12 7:35 ` Emmanuel Grumbach
2014-06-12 7:43 ` Arend van Spriel
2014-06-12 12:43 ` 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=1402577025.8095.16.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aaro.koskinen@iki.fi \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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