From: Luciano Coelho <coelho@ti.com>
To: linux-wireless@vger.kernel.org
Cc: stable@kernel.org, yoni.divinsky@ti.com
Subject: Re: [PATCH v2] wl12xx: fix forced passive scans
Date: Thu, 22 Sep 2011 13:22:15 +0300 [thread overview]
Message-ID: <1316686935.2157.572.camel@cumari> (raw)
In-Reply-To: <1316677732-2242-1-git-send-email-coelho@ti.com>
On Thu, 2011-09-22 at 10:48 +0300, Luciano Coelho wrote:
> We were using incorrect max and min dwell times during forced passive
> scans because we were still using the active scan states to scan
> (passively) the channels that were not marked as passive.
>
> Instead of doing passive scans in active states, we now skip active
> states and scan for all channels in passive states.
>
> Cc: <stable@kernel.org> # 2.6.36+
> Signed-off-by: Luciano Coelho <coelho@ti.com>
> ---
Applied.
--
Cheers,
Luca.
prev parent reply other threads:[~2011-09-22 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 7:30 [PATCH] wl12xx: fix forced passive scans Luciano Coelho
2011-09-22 7:48 ` [PATCH v2] " Luciano Coelho
2011-09-22 10:22 ` Luciano Coelho [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=1316686935.2157.572.camel@cumari \
--to=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@kernel.org \
--cc=yoni.divinsky@ti.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