From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Janusz Dziedzic <janusz.dziedzi@tieto.com>
Subject: Re: [PATCH v2 1/3] cfg80211: add helper reg_get_regdomain() function
Date: Wed, 29 Jan 2014 09:17:52 +0100 [thread overview]
Message-ID: <1390983472.4143.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6VfmOMVT3zxE1iEOtT53SycgrrpiKuoi2NPuDXvccz96Q@mail.gmail.com> (sfid-20140128_204258_986741_2295FC10)
On Tue, 2014-01-28 at 11:42 -0800, Luis R. Rodriguez wrote:
> > You mean we should introduce:
> > iw wlanX reg get?
>
> Sure, and iw dev reg get can also display what it does now but then
> also iterate over all wiphys and also display all wiphy's own regd if
> they have any.
I'm not really sure I see much point in all this - what userspace
eventually cares about isn't the reg data but the channel list that can
be obtained with (the equivalent of) iw list.
johannes
next prev parent reply other threads:[~2014-01-29 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 12:43 [PATCH v2 1/3] cfg80211: add helper reg_get_regdomain() function Janusz Dziedzic
2014-01-22 12:43 ` [PATCH v2 2/3] cfg80211: introduce regulatory wide bandwidth flag Janusz Dziedzic
2014-01-23 15:57 ` Johannes Berg
2014-01-25 0:32 ` Luis R. Rodriguez
2014-01-25 0:36 ` Luis R. Rodriguez
2014-01-25 10:29 ` Janusz Dziedzic
2014-01-29 13:10 ` Johannes Berg
2014-01-30 0:41 ` Luis R. Rodriguez
2014-01-31 13:42 ` Johannes Berg
2014-01-22 12:43 ` [PATCH v2 3/3] cfg80211: parse WIDE-BW flag for internal regdb option Janusz Dziedzic
2014-01-25 0:34 ` [PATCH v2 1/3] cfg80211: add helper reg_get_regdomain() function Luis R. Rodriguez
2014-01-28 19:23 ` Janusz Dziedzic
2014-01-28 19:42 ` Luis R. Rodriguez
2014-01-29 8:17 ` Johannes Berg [this message]
2014-01-29 9:44 ` Luis R. Rodriguez
2014-01-29 9:46 ` Luis R. Rodriguez
2014-01-29 9:58 ` Johannes Berg
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=1390983472.4143.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzi@tieto.com \
--cc=janusz.dziedzic@tieto.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