| Message ID | 20120802002723.7762E2056A@glenhelen.mtv.corp.google.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Wed, 2012-08-01 at 16:54 -0700, Paul Stewart wrote: > Restore the default state to the "beacon_found" flag when > the channel flags are restored. Otherwise, we can end up > with a channel that we can no longer transmit on even when > we can see beacons on that channel. Makes sense, applied. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/net/wireless/reg.c b/net/wireless/reg.c index 2303ee7..cc6b4c4 100644 --- a/net/wireless/reg.c +++ b/net/wireless/reg.c @@ -1885,6 +1885,7 @@ static void restore_custom_reg_settings(struct wiphy *wiphy) chan->flags = chan->orig_flags; chan->max_antenna_gain = chan->orig_mag; chan->max_power = chan->orig_mpwr; + chan->beacon_found = false; } } }
Restore the default state to the "beacon_found" flag when the channel flags are restored. Otherwise, we can end up with a channel that we can no longer transmit on even when we can see beacons on that channel. Signed-off-by: Paul Stewart <pstew@chromium.org> --- net/wireless/reg.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)