From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Ilan Peer <ilan.peer@intel.com>,
linux-wireless@vger.kernel.org, mcgrof@do-not-panic.com
Subject: Re: [PATCH 2/3] [RFC] cfg80211: Add Kconfig option for cellular BS hints
Date: Tue, 02 Jul 2013 16:00:47 +0200 [thread overview]
Message-ID: <1372773647.8615.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51D2DBB9.4010500@broadcom.com> (sfid-20130702_155518_357097_AF2DF864)
On Tue, 2013-07-02 at 15:55 +0200, Arend van Spriel wrote:
> On 07/02/2013 02:28 PM, Ilan Peer wrote:
> > Move the regulatory cellular base station hints support under
> > a specific configuration option and make the option depend
> > on CFG80211_CERTIFICATION_ONUS.
>
> This one seems not really related to the other patches. On itself it is
> not clear to me what itch is being scratched here. Is the aim to get rid
> of the CERTIFICATION_ONUS dependency further along the road?
No, it's really just so patch 3 can add a separate option under
CERTIFICATION_ONUS while allowing cell base station and the new option
to be separate.
johannes
next prev parent reply other threads:[~2013-07-02 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 12:28 [PATCH 0/3] Enable additional channels for GO Ilan Peer
2013-07-02 12:28 ` [PATCH 1/3] [RFC] cfg80211: Add indoor only and GO concurrent channel attributes Ilan Peer
2013-07-08 21:45 ` Luis R. Rodriguez
2013-07-10 10:43 ` Peer, Ilan
2013-07-16 20:43 ` Luis R. Rodriguez
2013-07-17 18:47 ` Peer, Ilan
2013-07-18 23:30 ` Luis R. Rodriguez
2013-07-02 12:28 ` [PATCH 2/3] [RFC] cfg80211: Add Kconfig option for cellular BS hints Ilan Peer
2013-07-02 13:55 ` Arend van Spriel
2013-07-02 14:00 ` Johannes Berg [this message]
2013-07-02 14:13 ` Arend van Spriel
2013-07-02 12:28 ` [PATCH 3/3] [RFC] cfg80211: Enable GO operation on additional channels Ilan Peer
2013-07-08 10:04 ` Jouni Malinen
2013-07-09 5:40 ` Peer, Ilan
2013-07-08 22:04 ` Luis R. Rodriguez
2013-07-10 10:47 ` Peer, Ilan
2013-07-16 20:57 ` Luis R. Rodriguez
2013-07-17 19:15 ` Peer, Ilan
2013-07-18 23:34 ` Luis R. Rodriguez
2013-10-04 17:38 ` Luis R. Rodriguez
2013-10-06 11:28 ` 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=1372773647.8615.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--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).