On Wed, Jun 04, 2014 at 07:02:24PM +0000, Grumbach, Emmanuel wrote: > > On Sun, May 18, 2014 at 11:21:40AM +0300, Emmanuel Grumbach wrote: > > > From: Alexander Bondar <[email protected]> > > > > > > commit c63722cfd441bd3a99c65fa4c40bc65d7776e772 upstream > > > > > > Enable beacon filter only if at least one beacon from candidate AP is > > > received before or after association. Check this condition before > > > enabling BF upon secured association completion. Add BF enablement to > > > mac80211 event that indicates beacon is received after association. > > > Too early beacon filtering enablement can lead to disconnection due to > > > missing AP's beacon after association. > > > > > > Signed-off-by: Alexander Bondar <[email protected]> > > > Signed-off-by: Emmanuel Grumbach <[email protected]> > > > --- > > > > This breaks the build on 3.14, so despite sending out the email that said I > > applied it, I had to revert it. Please test-build your patches before > > sending > > them... > > > > Sorry for that... In any case, this patch is not needed, now that > 7bacc782270ff7db3b9f29fa5d24ad2ee1e8e81d hit Linus's tree (and is > badly needed in 3.14 / 3.13).
Now queued up for 3.14-stable, thanks. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
