From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH v5 1/4] cfg80211: leave invalid channels on regdomain change
Date: Fri, 28 Nov 2014 14:44:38 +0100 [thread overview]
Message-ID: <1417182278.27562.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1417074298-12254-1-git-send-email-arik@wizery.com> (sfid-20141127_084458_008782_038693EB)
On Thu, 2014-11-27 at 09:44 +0200, Arik Nemtsov wrote:
> When the regulatory settings change, some channels might become invalid.
> Disconnect interfaces acting on these channels, after giving userspace
> code a grace period to leave them.
>
> This mode is currently opt-in, and not all interface operating modes are
> supported for regulatory-enforcement checks. A wiphy that wishes to use
> the new enforcement code must specify an appropriate regulatory flag,
> and all its supported interface modes must be supported by the chekcing
> code.
Applied, with some trivial changes.
johannes
prev parent reply other threads:[~2014-11-28 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 7:44 [PATCH v5 1/4] cfg80211: leave invalid channels on regdomain change Arik Nemtsov
2014-11-27 7:44 ` [PATCH v5 2/4] cfg80211: allow usermode to query wiphy specific regdom Arik Nemtsov
2014-11-28 13:46 ` Johannes Berg
2014-11-28 22:00 ` Luis R. Rodriguez
2014-11-30 12:26 ` Arik Nemtsov
2014-11-30 12:32 ` Johannes Berg
2014-11-30 12:36 ` Arik Nemtsov
2014-11-28 22:03 ` Luis R. Rodriguez
2014-11-27 7:44 ` [PATCH v5 3/4] cfg80211: allow wiphy specific regdomain management Arik Nemtsov
2014-11-28 13:53 ` Johannes Berg
2014-11-27 7:44 ` [PATCH v5 4/4] cfg80211: return private regdom for self-managed devices Arik Nemtsov
2014-11-28 13:57 ` Johannes Berg
2014-11-28 13:44 ` 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=1417182278.27562.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.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