From: Luciano Coelho <coelho@ti.com>
To: Eyal Shapira <eyal@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: mark no sched scan only after FW event
Date: Tue, 20 Dec 2011 22:51:18 +0200 [thread overview]
Message-ID: <1324414278.2182.76.camel@cumari> (raw)
In-Reply-To: <1324385738-3132-1-git-send-email-eyal@wizery.com>
On Tue, 2011-12-20 at 14:55 +0200, Eyal Shapira wrote:
> stop sched scan isn't an immediate operation
> and we need to wait for PERIODIC_SCAN_COMPLETE_EVENT_ID
> after sending a stop before changing internal state
> and notifying upper layers.
> Not doing this caused problems when canceling an existing sched
> scan and immediately requesting to start a new one
> with a different configuration as the FW was still
> in the middle of the previous sched scan.
>
> Signed-off-by: Eyal Shapira <eyal@wizery.com>
> ---
Applied, thanks!
--
Cheers,
Luca.
prev parent reply other threads:[~2011-12-20 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 12:55 [PATCH] wl12xx: mark no sched scan only after FW event Eyal Shapira
2011-12-20 20:51 ` 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=1324414278.2182.76.camel@cumari \
--to=coelho@ti.com \
--cc=eyal@wizery.com \
--cc=linux-wireless@vger.kernel.org \
/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