linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [PATCH v3 3/6] cfg80211: Enable GO operation on additional channels
Date: Fri, 31 Jan 2014 15:11:19 +0100	[thread overview]
Message-ID: <1391177479.4141.23.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1390818118-27261-4-git-send-email-ilan.peer@intel.com> (sfid-20140127_112147_514798_01405A03)

On Mon, 2014-01-27 at 12:21 +0200, Ilan Peer wrote:

> It is assumed that such restrictions are enforced by user space.
> Furthermore, it is assumed, that if the conditions that allowed for
> the operation of the GO on such a channel change, i.e., the station
> interface disconnected from the AP, it is the responsibility of user
> space to evacuate the GO from the channel.

For the latter here, don't we need some sort of flag with userspace
saying "trust me, I know what I'm doing"? Or put another way - how does
this not make us break compliance when running with old versions of
wpa_supplicant?

johannes


  reply	other threads:[~2014-01-31 14:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 10:21 [PATCH v3 0/6] Enable additional channels for use Ilan Peer
2014-01-27 10:21 ` [PATCH v3 1/6] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-02-18 22:49   ` Luis R. Rodriguez
2014-02-19 14:44     ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 2/6] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-02-18 22:59   ` Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-01-31 14:11   ` Johannes Berg [this message]
2014-02-02 19:20     ` Peer, Ilan
2014-02-03 12:46       ` Johannes Berg
2014-02-03 13:24         ` Peer, Ilan
2014-02-18 23:38   ` Luis R. Rodriguez
2014-02-19 14:52     ` Peer, Ilan
2014-02-19 15:47       ` Luis R. Rodriguez
2014-02-20  7:31         ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 4/6] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-01-31 14:13   ` Johannes Berg
2014-02-03 11:14   ` Ilan Peer
2014-02-19  0:07   ` Luis R. Rodriguez
2014-02-19 15:18     ` Peer, Ilan
2014-01-27 10:21 ` [PATCH v3 5/6] cfg80211: Enable GO operation on indoor channels Ilan Peer
2014-02-19  0:10   ` Luis R. Rodriguez
2014-01-27 10:21 ` [PATCH v3 6/6] mac80211: Enable initiating radiation " Ilan Peer
2014-02-19  0:15   ` Luis R. Rodriguez
2014-02-19 15:28     ` Peer, Ilan
2014-02-19 16:03       ` Luis R. Rodriguez
2014-02-20  7:58         ` Peer, Ilan
2014-02-21 23:31           ` Luis R. Rodriguez
2014-02-22 18:55             ` Peer, Ilan
2014-02-22 20:22               ` Luis R. Rodriguez
2014-02-23  7:23                 ` Peer, Ilan
2014-02-23  9:43                   ` Luis R. Rodriguez
2014-01-27 10:24 ` [PATCH v3 0/6] Enable additional channels for use Peer, Ilan
2014-02-09 16:06 ` Peer, Ilan
2014-02-18 22:17   ` Luis R. Rodriguez
2014-02-18 22:18     ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2013-12-03 19:16 [PATCH v2 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2013-12-05 13:57 ` [PATCH v3 " Ilan Peer

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=1391177479.4141.23.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ilan.peer@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-regdb@lists.infradead.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).