From: Johannes Berg <johannes@sipsolutions.net>
To: "Chauhan, Rajesh" <rajeshc@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"Malinen, Jouni" <jouni@qca.qualcomm.com>,
"Bahini, Henri" <hbahini@qca.qualcomm.com>,
"Chang, Leo" <schang@qca.qualcomm.com>,
"Luo, Xun" <xunl@qca.qualcomm.com>
Subject: Re: [PATCH] cfg80211/nl80211: Add support to report unsafe frequency ranges(s)
Date: Mon, 28 Oct 2013 15:44:39 +0100 [thread overview]
Message-ID: <1382971479.17956.29.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <D19FD2B13A40CD4B8DA64DB9B8F112E9218DAC92@nasanexd01a.na.qualcomm.com>
On Thu, 2013-10-17 at 17:19 +0000, Chauhan, Rajesh wrote:
> Hi Johannes,
>
> Thanks for your comment. Purpose of this patch is to add an API for
> WLAN driver to report frequency ranges which should be avoided for
> SAP/P2P-GO because of interference.
>
> How about if I reword commit test as below?
>
> cfg80211/nl80211: Add API to report frequency range(s) to be avoided
>
> Add support for WLAN driver to report frequency range(s) to be avoided
> because of interference.
Wouldn't it make more sense to raise a "detected interference" event?
There's no way to know what channel range is affected anyway. I fear
that this is vague enough for you to (ab)use it for all kinds of random
"channel steering" from the driver.
johannes
next prev parent reply other threads:[~2013-10-28 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 4:57 [PATCH] cfg80211/nl80211: Add support to report unsafe frequency ranges(s) Rajesh Chauhan
2013-10-17 14:40 ` Johannes Berg
2013-10-17 17:19 ` Chauhan, Rajesh
2013-10-28 14:44 ` Johannes Berg [this message]
2013-10-28 18:14 ` Chauhan, Rajesh
2013-10-17 17:46 ` Chauhan, Rajesh
2013-10-17 18:39 ` Dan Williams
2013-10-17 19:51 ` Chauhan, Rajesh
2013-10-20 10:39 ` Luis R. Rodriguez
2013-10-28 18:08 ` Chauhan, Rajesh
2013-10-28 19:01 ` Dan Williams
2013-10-28 21:11 ` Jeffrey Johnson
2013-10-29 10:30 ` Luis R. Rodriguez
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=1382971479.17956.29.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=hbahini@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajeshc@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=schang@qca.qualcomm.com \
--cc=xunl@qca.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox