From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Ilan Peer <ilan.peer@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v10 3/3] cfg80211: Schedule timeout for all CRDA calls
Date: Fri, 06 Mar 2015 09:39:32 +0100 [thread overview]
Message-ID: <1425631172.3339.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20150305225526.GC25035@wotan.suse.de> (sfid-20150305_235530_475137_C30BAA08)
On Thu, 2015-03-05 at 23:55 +0100, Luis R. Rodriguez wrote:
> On Wed, Mar 04, 2015 at 12:32:07AM -0500, Ilan Peer wrote:
> > Timeout was scheduled only in case CRDA was called due to user hints,
> > but was not scheduled for other cases. This can result in regulatory
> > hint processing getting stuck in case that there is no CRDA configured.
> >
> > Change this by scheduling a timeout every time CRDA is called. In
> > addition, in restore_regulatory_settings() all pending requests are
> > restored (and not only the user ones).
> >
> > Signed-off-by: Ilan Peer <ilan.peer@intel.com>
>
> Acked-by: Luis R. Rodriguez <mcgrof@suse.com>
>
> For all of these.
Great, all three applied, thanks guys.
johannes
next prev parent reply other threads:[~2015-03-06 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 5:32 [PATCH v10 1/3] cfg80211: Simplify the handling of regulatory indoor setting Ilan Peer
2015-03-04 5:32 ` [PATCH v10 2/3] cfg80211: Add API to change the indoor regulatory setting Ilan Peer
2015-03-05 22:54 ` Luis R. Rodriguez
2015-03-04 5:32 ` [PATCH v10 3/3] cfg80211: Schedule timeout for all CRDA calls Ilan Peer
2015-03-05 22:55 ` Luis R. Rodriguez
2015-03-06 8:39 ` Johannes Berg [this message]
2015-03-08 7:34 ` Peer, Ilan
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=1425631172.3339.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@suse.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).