From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, gregoryx.alagnou@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/2] cfg80211: fix regulatory restore upon user hints
Date: Fri, 01 Apr 2011 21:59:08 +0200 [thread overview]
Message-ID: <1301687948.3842.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1301686955-9402-1-git-send-email-lrodriguez@atheros.com>
On Fri, 2011-04-01 at 12:42 -0700, Luis R. Rodriguez wrote:
> When we restore regulatory settings its possible CRDA
> will not reply because of a bogus user entry. In this
> case the bogus entry will prevent any further processing
> on cfg80211 for regulatory domains even if we restore
> regulatory settings.
>
> To prevent this we suck out all pending requests when
> restoring regulatory settings and add them back into the
> queue after we have queued up the reset work.
What if CRDA replies in order, i.e. replies to the user requested one
first instead of the disassoc requested one?
Why do we even require crda to reply to the first in list, rather than
any one?
johannes
next prev parent reply other threads:[~2011-04-01 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 19:42 [PATCH v3 1/2] cfg80211: fix regulatory restore upon user hints Luis R. Rodriguez
2011-04-01 19:59 ` Johannes Berg [this message]
2011-04-01 20:10 ` Luis R. Rodriguez
2011-04-01 20:28 ` Johannes Berg
2011-04-01 21:47 ` Luis R. Rodriguez
2011-04-01 21:49 ` Johannes Berg
2011-04-01 22:22 ` Luis R. Rodriguez
2011-04-04 12:19 ` Johannes Berg
2011-04-04 19:57 ` Luis R. Rodriguez
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=1301687948.3842.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gregoryx.alagnou@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).