From: Johannes Berg <johannes@sipsolutions.net>
To: Ilan Peer <ilan.peer@intel.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@do-not-panic.com
Subject: Re: [PATCH v5 4/5] cfg80211: Add an option to hint indoor operation
Date: Fri, 21 Feb 2014 10:02:59 +0100 [thread overview]
Message-ID: <1392973379.4346.41.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1392898909-15953-1-git-send-email-ilan.peer@intel.com> (sfid-20140220_131946_336789_F6B979EE)
On Thu, 2014-02-20 at 14:21 +0200, Ilan Peer wrote:
> +bool regulatory_indoor_allowed(void)
> +{
> + return reg_is_indoor;
> +}
> +EXPORT_SYMBOL_GPL(regulatory_indoor_allowed);
I don't see any user of this (in particular none that would need it
exported)?
johannes
next prev parent reply other threads:[~2014-02-21 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 11:44 [PATCH v5 0/5] Enable additional channels for use Ilan Peer
2014-02-20 11:44 ` [PATCH v5 1/5] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2014-02-21 23:36 ` Luis R. Rodriguez
2014-02-20 11:44 ` [PATCH v5 2/5] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2014-02-21 23:37 ` Luis R. Rodriguez
2014-02-20 11:44 ` [PATCH v5 3/5] cfg80211: Enable GO operation on additional channels Ilan Peer
2014-02-22 0:06 ` Luis R. Rodriguez
2014-02-20 11:44 ` [PATCH 4/5] cfg80211: Add an option to hint indoor operation Ilan Peer
2014-02-20 12:21 ` [PATCH v5 " Ilan Peer
2014-02-21 9:02 ` Johannes Berg [this message]
2014-02-22 20:16 ` Peer, Ilan
2014-02-22 0:28 ` [PATCH " Luis R. Rodriguez
2014-02-22 20:00 ` Peer, Ilan
2014-02-22 21:10 ` Luis R. Rodriguez
2014-02-20 11:44 ` [PATCH v5 5/5] cfg80211: Enable GO operation on indoor channels Ilan Peer
2014-02-22 0:09 ` Luis R. Rodriguez
2014-02-22 19:54 ` Peer, Ilan
2014-02-22 21:08 ` Luis R. Rodriguez
2014-02-23 7:21 ` Peer, Ilan
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=1392973379.4346.41.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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;
as well as URLs for NNTP newsgroup(s).