From: Johannes Berg <johannes@sipsolutions.net>
To: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC V2 0/3] Pre-CAC and sharing DFS state across multiple radios
Date: Mon, 20 Feb 2017 10:15:59 +0100 [thread overview]
Message-ID: <1487582159.5474.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1487262275-14654-1-git-send-email-vthiagar@qti.qualcomm.com>
On Thu, 2017-02-16 at 21:54 +0530, Vasanthakumar Thiagarajan wrote:
> Currently irrespective of dfs domain and radar detection activity
> pre-CAC results for a wiphy are retained till the wiphy is detroyed.
> This may not be preferred in non-ETSI dfs domain where pre-CAC is not
> explicitly mentioned in the respective DFS requirement spec. This
> patch
> set modifies the current behaviour of pre-CAC for non-ETSI domain by
> giving 2 seconds grace period for dfs master interface to start
> operating
> on the CAC completed channel.
>
> This patch set also adds support to share dfs channel state across
> multiple radios of the same regulatory configuration.
>
Looks fine to me - please resend as PATCH.
johannes
prev parent reply other threads:[~2017-02-20 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 16:24 [RFC V2 0/3] Pre-CAC and sharing DFS state across multiple radios Vasanthakumar Thiagarajan
2017-02-16 16:24 ` [RFC V2 1/3] cfg80211: Make pre-CAC results valid only for ETSI domain Vasanthakumar Thiagarajan
2017-02-16 16:24 ` [RFC V2 2/3] cfg80211: Disallow moving out of operating DFS channel in non-ETSI Vasanthakumar Thiagarajan
2017-02-16 16:24 ` [RFC V2 3/3] cfg80211: Share Channel DFS state across wiphys of same DFS domain Vasanthakumar Thiagarajan
2017-02-20 9:15 ` 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=1487582159.5474.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vthiagar@qti.qualcomm.com \
/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.