From: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
To: <johannes@sipsolutions.net>
Cc: <linville@tuxdriver.com>, <linux-wireless@vger.kernel.org>,
Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Subject: [PATCH 2/2] mac80211: fix oper channel timestamp updation
Date: Mon, 26 Mar 2012 20:53:38 +0530 [thread overview]
Message-ID: <1332775418-16865-2-git-send-email-rmanohar@qca.qualcomm.com> (raw)
In-Reply-To: <1332775418-16865-1-git-send-email-rmanohar@qca.qualcomm.com>
At the start of scan, mac80211 stop all vif transmission and inform the
AP that the station is leaving the operating channel. But it is not
updating the leave_oper_channel timestamp. As the result, the scan
decision always set operating channel at the scan start when the listen
interval is reduced.
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
---
net/mac80211/scan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
index 33cd169..c70e176 100644
--- a/net/mac80211/scan.c
+++ b/net/mac80211/scan.c
@@ -370,7 +370,7 @@ static int ieee80211_start_sw_scan(struct ieee80211_local *local)
*/
drv_sw_scan_start(local);
- local->leave_oper_channel_time = 0;
+ local->leave_oper_channel_time = jiffies;
local->next_scan_state = SCAN_DECISION;
local->scan_channel_idx = 0;
--
1.7.9.4
next prev parent reply other threads:[~2012-03-26 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:23 [PATCH 1/2] mac80211: inform the offchannel status to AP if no powersave Rajkumar Manoharan
2012-03-26 15:23 ` Rajkumar Manoharan [this message]
2012-03-26 16:09 ` [PATCH 2/2] mac80211: fix oper channel timestamp updation Johannes Berg
2012-03-26 21:37 ` Helmut Schaa
2012-03-26 16:09 ` [PATCH 1/2] mac80211: inform the offchannel status to AP if no powersave Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2012-03-26 15:23 Rajkumar Manoharan
2012-03-26 15:23 ` [PATCH 2/2] mac80211: fix oper channel timestamp updation Rajkumar Manoharan
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=1332775418-16865-2-git-send-email-rmanohar@qca.qualcomm.com \
--to=rmanohar@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).