From: Johannes Berg <johannes@sipsolutions.net>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: linux-wireless@vger.kernel.org,
Antonio Quartulli <antonio@open-mesh.com>
Subject: Re: [PATCH v3] mac80211: do not actively scan DFS channels
Date: Thu, 26 Nov 2015 18:05:34 +0100 [thread overview]
Message-ID: <1448557534.2167.25.camel@sipsolutions.net> (raw)
In-Reply-To: <1448100820-22567-1-git-send-email-antonio@meshcoding.com>
On Sat, 2015-11-21 at 18:13 +0800, Antonio Quartulli wrote:
> DFS channels should not be actively scanned as we can't be sure
> if we are allowed or not.
>
> If the current channel is in the DFS band, active scan might be
> performed after CSA, but we have no guarantee about other channels,
> therefore it is safer to prevent active scanning at all.
>
Applied to mac80211.git, also added cc stable. I modified the code a
bit to be shorter :)
johannes
prev parent reply other threads:[~2015-11-26 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 10:13 [PATCH v3] mac80211: do not actively scan DFS channels Antonio Quartulli
2015-11-26 17:05 ` 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=1448557534.2167.25.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=antonio@meshcoding.com \
--cc=antonio@open-mesh.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).