linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arik Nemtsov <arik@wizery.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	linux@eikelenboom.it
Subject: Re: [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier
Date: Thu, 27 Feb 2014 15:21:35 +0200	[thread overview]
Message-ID: <CA+XVXffSTA__zwYDzzyHB2B1mLZaL0sXT8prmUvdb-w_QA4_pg@mail.gmail.com> (raw)
In-Reply-To: <1393376982-28276-4-git-send-email-mcgrof@do-not-panic.com>

On Wed, Feb 26, 2014 at 3:09 AM, Luis R. Rodriguez
<mcgrof@do-not-panic.com> wrote:
> This adds a trigger to review any pending regulatory
> requests whenever an 802.11 device interface is brought
> down or up. We use this as an opportunistic trigger
> for checking the regulatory work queues as otherwise
> they they're only checked upon an initial regulatory
> request or when beacon hints are found.
>
> This opportunistic mechanism can be used to trigger
> kicking the queues regulatory queues at any time from
> userspace without having to change the regulatory state.
>
> A timer just waiting upon init is not that appropriate
> as when it should be triggered will depend on systems,
> a much better approach is to use and add opportunistic
> triggers. The interface coming up is typically a good
> indicator that filesystems have been mounted since
> firmware is required for some devices.
>
> Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
> Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
> ---
>  net/wireless/reg.h | 1 +
>  1 file changed, 1 insertion(+)

Seems the actual patch is missing?

Arik

  reply	other threads:[~2014-02-27 13:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  1:09 [PATCH v2 0/3] cfg80211: respin reprocessing pending requests Luis R. Rodriguez
2014-02-26  1:09 ` [PATCH 1/3] cfg80211: allow reprocessing of " Luis R. Rodriguez
2014-03-03 13:10   ` Johannes Berg
2014-02-26  1:09 ` [PATCH 2/3] cfg80211: fix processing world regdomain when non modular Luis R. Rodriguez
2014-03-03 13:10   ` Johannes Berg
2014-03-14 20:30     ` Colleen T
2014-03-14 20:48       ` Luis R. Rodriguez
2014-03-14 22:12         ` Colleen T
2014-03-15  1:03           ` Luis R. Rodriguez
2014-03-15 15:59             ` Janusz Dziedzic
2014-03-16  4:42               ` Luis R. Rodriguez
2014-03-16 19:04                 ` Colleen T
2014-04-09 16:33                   ` Arik Nemtsov
2014-04-09 19:16                     ` Johannes Berg
2014-04-10  6:13                       ` Arik Nemtsov
2014-04-10  8:01                         ` Johannes Berg
2014-04-10  8:17                           ` Arik Nemtsov
2014-04-10  8:23                             ` Johannes Berg
2014-04-09 20:28                     ` Sander Eikelenboom
2014-04-13 12:50                     ` Eliad Peller
2014-04-14 19:27                       ` Colleen T
2014-04-16 10:38                         ` Arik Nemtsov
2014-04-16 11:01                           ` Janusz Dziedzic
2014-04-16 11:07                             ` Arik Nemtsov
2014-03-19 14:01       ` Johannes Berg
2014-02-26  1:09 ` [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier Luis R. Rodriguez
2014-02-27 13:21   ` Arik Nemtsov [this message]
2014-02-27 17:20     ` Luis R. Rodriguez
2014-02-27 20:31       ` Arik Nemtsov
2014-02-26  7:41 ` [PATCH v2 0/3] cfg80211: respin reprocessing pending requests Sander Eikelenboom
  -- strict thread matches above, loose matches on Subject: below --
2013-12-19 20:53 [PATCH 0/3] cfg80211: process pending regulatory requests Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier Luis R. Rodriguez
2014-01-07 15:35   ` Johannes Berg
2014-02-19  1:24     ` Luis R. Rodriguez
2014-02-19 18:08       ` 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=CA+XVXffSTA__zwYDzzyHB2B1mLZaL0sXT8prmUvdb-w_QA4_pg@mail.gmail.com \
    --to=arik@wizery.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=mcgrof@do-not-panic.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).