From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: allow some multi-channel combinations with DFS master
Date: Sun, 21 Dec 2014 23:09:48 +0100 [thread overview]
Message-ID: <1419199788.2387.5.camel@sipsolutions.net> (raw)
In-Reply-To: <1419179546-29313-2-git-send-email-eliad@wizery.com> (sfid-20141221_173231_578831_6AC3F6DF)
On Sun, 2014-12-21 at 18:32 +0200, Eliad Peller wrote:
> Allow some multi-channel interface combinations along with
> DFS master support, if there is only a single AP/GO.
>
> Allowing other interface types at the same time is fine
I don't believe this to be true - how are you going to do radar
detection accurately if you're spending any amount of time on another
channel?
johannes
next prev parent reply other threads:[~2014-12-21 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 16:32 [PATCH 1/2] mac80211: consider only relevant vifs for radar_required calculation Eliad Peller
2014-12-21 16:32 ` [PATCH 2/2] mac80211: allow some multi-channel combinations with DFS master Eliad Peller
2014-12-21 22:09 ` Johannes Berg [this message]
2014-12-22 22:26 ` Eliad Peller
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=1419199788.2387.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.