From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [PATCH v2 6/6] mac80211: Enable initiating radiation on indoor channels
Date: Fri, 24 Jan 2014 16:21:36 -0800 [thread overview]
Message-ID: <20140125002134.GC28512@garbanzo.do-not-panic.com> (raw)
In-Reply-To: <1389801162-14488-7-git-send-email-ilan.peer@intel.com>
On Wed, Jan 15, 2014 at 05:52:42PM +0200, Ilan Peer wrote:
> + if (!regulatory_ir_allowed(req->channels[0]) ||
Please keep in mind that the feature flag on the wiphy would
be used in your regulatory_ir_allowed() routine.
Luis
next prev parent reply other threads:[~2014-01-25 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 15:52 [PATCH v2 0/6] Enable additional channels for use Ilan Peer
2014-01-15 15:52 ` [PATCH v2 1/6] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-01-15 15:52 ` [PATCH v2 2/6] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-01-15 15:52 ` [PATCH v2 3/6] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-01-25 0:09 ` Luis R. Rodriguez
2014-01-26 22:03 ` Peer, Ilan
2014-01-26 22:21 ` Peer, Ilan
2014-01-27 8:41 ` Peer, Ilan
2014-01-15 15:52 ` [PATCH v2 4/6] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-01-25 0:20 ` Luis R. Rodriguez
2014-01-26 22:11 ` Peer, Ilan
2014-02-18 22:22 ` Luis R. Rodriguez
2014-01-15 15:52 ` [PATCH v2 5/6] cfg80211: Enable GO operation on indoor channels Ilan Peer
2014-01-15 15:52 ` [PATCH v2 6/6] mac80211: Enable initiating radiation " Ilan Peer
2014-01-25 0:21 ` Luis R. Rodriguez [this message]
2014-01-25 0:24 ` [PATCH v2 0/6] Enable additional channels for use Luis R. Rodriguez
2014-01-26 22:13 ` Peer, Ilan
-- strict thread matches above, loose matches on Subject: below --
2013-12-03 19:16 Ilan Peer
2013-12-03 19:16 ` [PATCH v2 6/6] mac80211: Enable initiating radiation on indoor channels Ilan Peer
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=20140125002134.GC28512@garbanzo.do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.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).