All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <rmani@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH] ath6kl: Store scan request info in-advance before sending SCAN request
Date: Wed, 28 Mar 2012 16:38:50 +0300	[thread overview]
Message-ID: <4F73146A.7000308@qca.qualcomm.com> (raw)
In-Reply-To: <1332940835-14933-1-git-send-email-rmani@qca.qualcomm.com>

On 03/28/2012 04:20 PM, rmani@qca.qualcomm.com wrote:
> From: Raja Mani <rmani@qca.qualcomm.com>
> 
> In current code, Scan request info is recorded in vif->scan_req
> after sending SCAN request to the firmware in ath6kl_cfg80211_scan().
> 
> In some corner cases, firmware sends SCAN_COMPLETE event immediately
> when it receives SCAN request, which internally executes scan
> complete event handler ath6kl_cfg80211_scan_complete_event() first.
> So, Scan completion handler will a get a chance to executed even
> before storing scan request info in ath6kl_cfg80211_scan().
> 
> Scan completion handler never report SCAN_COMPLETE event to
> cfg80211 if scan request info(vif->scan_req) is NULL. This leads
> to scan failure issue ("Device or resource busy error") during
> next SCAN request from the user space. This patch ensures that scan
> request info is stored before sending SCAN request.
> 
> Signed-off-by: Raja Mani <rmani@qca.qualcomm.com>

Thanks, applied.

Kalle

      reply	other threads:[~2012-03-28 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 13:20 [PATCH] ath6kl: Store scan request info in-advance before sending SCAN request rmani
2012-03-28 13:38 ` Kalle Valo [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=4F73146A.7000308@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmani@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.