From: Johannes Berg <johannes@sipsolutions.net>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 5/6] cfg80211: reg: make CRDA support optional
Date: Fri, 16 Oct 2015 08:37:33 +0200 [thread overview]
Message-ID: <1444977453.2370.2.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGRGNgUZXfrmCA+KpgTW2_yFEqVao7DmQofNrFpiiRAWhUaYXw@mail.gmail.com> (sfid-20151016_010415_028531_DF68F6E6)
> > config CFG80211_INTERNAL_REGDB
> >
> > +config CFG80211_CRDA_SUPPORT
>
> Is there a way to force the kernel builder to select at least one of
> these if they're building cfg80211?
>
I'd actually thought about that, but I think there are two reasons not
to.
1) it may actually be a valid configuration, if you really only need
the built-in world regulatory domain, or have a device that provides
its own
2) the [RFC] patch I sent will add a *third* mechanism (and the second
one will remove the INTERNAL_REGDB support) so there would only be a
transition period
That said, perhaps since (2) will probably be significantly later than
this patch there could still be a point in it. (1) isn't very strong
and I don't even preserve that after (2).
johannes
next prev parent reply other threads:[~2015-10-16 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 9:46 [PATCH 1/6] cfg80211: reg: remove useless non-NULL check Johannes Berg
2015-10-15 9:46 ` [PATCH 2/6] cfg80211: reg: rename reg_call_crda to reg_query_database Johannes Berg
2015-10-15 9:46 ` [PATCH 3/6] cfg80211: reg: search built-in database directly Johannes Berg
2015-10-15 9:46 ` [PATCH 4/6] cfg80211: reg: remove useless reg_timeout scheduling Johannes Berg
2015-10-15 9:46 ` [PATCH 5/6] cfg80211: reg: make CRDA support optional Johannes Berg
2015-10-15 23:03 ` Julian Calaby
2015-10-16 6:37 ` Johannes Berg [this message]
2015-10-15 9:46 ` [PATCH 6/6] cfg80211: reg: rename reg_regdb_query() to reg_query_builtin() 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=1444977453.2370.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.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).