From: Johannes Berg <johannes@sipsolutions.net>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org,
Avraham Stern <avraham.stern@intel.com>,
Arik Nemtsov <arikx.nemtsov@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH v3] cfg80211: Allow GO concurrent relaxation after BSS disconnection
Date: Wed, 06 May 2015 14:48:17 +0200 [thread overview]
Message-ID: <1430916497.1954.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1430142736-24032-1-git-send-email-ilan.peer@intel.com> (sfid-20150427_155022_871329_5457BC68)
On Mon, 2015-04-27 at 16:52 +0300, Ilan Peer wrote:
> From: Avraham Stern <avraham.stern@intel.com>
>
> If a P2P GO was allowed on a channel because of the GO concurrent
> relaxation, i.e., another station interface was associated to an AP on
> the same channel or the same UNII band, and the station interface
> disconnected from the AP, allow the following use cases unless the
> channel is marked as indoor only and the device is not operating in an
> indoor environment:
>
> 1. Allow the P2P GO to stay on its current channel. The rationale behind
> this is that if the channel or UNII band were allowed by the AP they
> could still be used to continue the P2P GO operation, and avoid connection
> breakage.
> 2. Allow another P2P GO to start on the same channel or another channel
> that is in the same UNII band as the previous instantiated P2P GO.
Applied.
johannes
prev parent reply other threads:[~2015-05-06 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 13:52 [PATCH v3] cfg80211: Allow GO concurrent relaxation after BSS disconnection Ilan Peer
2015-05-06 12:48 ` 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=1430916497.1954.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arikx.nemtsov@intel.com \
--cc=avraham.stern@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.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).