From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: implement STA CSA for drivers using channel contexts
Date: Wed, 02 Oct 2013 18:20:16 +0200 [thread overview]
Message-ID: <1380730816.13329.28.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1378044951-13682-1-git-send-email-arik@wizery.com> (sfid-20130901_161614_768170_0FA669D7)
On Sun, 2013-09-01 at 17:15 +0300, Arik Nemtsov wrote:
> Limit the current implementation to a single channel context used by
> a single vif, thereby avoiding multi-vif/channel complexities.
>
> Reuse the main function from AP CSA code, but move a portion out in
> order to fit the STA scenario.
>
> Add a new mac80211 HW flag so we don't break devices that don't support
> channel switch with channel-contexts. The new behavior will be opt-in.
Applied, sorry for the delay.
johannes
prev parent reply other threads:[~2013-10-02 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 14:15 [PATCH v2] mac80211: implement STA CSA for drivers using channel contexts Arik Nemtsov
2013-09-29 7:06 ` Arik Nemtsov
2013-10-02 11:44 ` Arik Nemtsov
2013-10-02 16:20 ` 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=1380730816.13329.28.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.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).