From: Valdis.Kletnieks@vt.edu
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ArikX Nemtsov <arik@wizery.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting
Date: Thu, 19 Feb 2015 20:03:05 -0500 [thread overview]
Message-ID: <36119.1424394185@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 20 Feb 2015 01:53:44 +0100." <20150220005344.GF20824@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
> Wider community:
>
> anyone aware of any *need* in the kernel to know whether one is indoor or
> not on a device running Linux other than wifi? Clearly it should be something
> that might be of interest to at least other RF devices, so that is at least
> one possibilty to consider already, but what else?
I can think of a lot of reasons for the kernel to make indoor/outdoor
status available to userspace, but am coming up empty why the kernel itself
should care....
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2015-02-20 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1422889166-29386-1-git-send-email-ilan.peer@intel.com>
[not found] ` <20150206235802.GA19988@wotan.suse.de>
[not found] ` <CB3B3D4774441E42AA3EA0E1BA8230A04D01068E@HASMSX106.ger.corp.intel.com>
[not found] ` <20150210200027.GG19988@wotan.suse.de>
[not found] ` <CB3B3D4774441E42AA3EA0E1BA8230A04D017CEB@HASMSX106.ger.corp.intel.com>
2015-02-20 0:53 ` Luis R. Rodriguez
2015-02-20 1:03 ` Valdis.Kletnieks [this message]
2015-02-20 2:09 ` Luis R. Rodriguez
2015-02-20 15:02 ` Jonathan Bither
2015-02-20 15:57 ` Luis R. Rodriguez
2015-02-22 7:57 ` 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=36119.1424394185@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=arik@wizery.com \
--cc=ilan.peer@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@suse.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
all inboxes | Powered by JetHome®