From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org,
Alexander Bondar <alexander.bondar@intel.com>
Subject: Re: [PATCH] mac80211: Release sched_scan_sdata when stopping sched scan
Date: Wed, 19 Mar 2014 15:01:49 +0100 [thread overview]
Message-ID: <1395237709.4142.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1394959794-19215-1-git-send-email-emmanuel.grumbach@intel.com>
On Sun, 2014-03-16 at 10:49 +0200, Emmanuel Grumbach wrote:
> From: Alexander Bondar <alexander.bondar@intel.com>
>
>
> Assuming sched_scan_stop operation is synchronous the driver may not
> necessary call ieee80211_sched_scan_stopped_work. Since this work is
> the only place where sched_scan_sdata is released we can possibly run
> into situation when it is never released. Fix this by releasing it
> just after calling drv_sched_scan_stop.
Applied.
johannes
prev parent reply other threads:[~2014-03-19 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 8:49 [PATCH] mac80211: Release sched_scan_sdata when stopping sched scan Emmanuel Grumbach
2014-03-19 14:01 ` Johannes Berg [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=1395237709.4142.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexander.bondar@intel.com \
--cc=emmanuel.grumbach@intel.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;
as well as URLs for NNTP newsgroup(s).