From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 27 Nov 2015 09:35:16 +0100
Subject: [ath9k-devel] [PATCH v2 6/8] cfg80211: reg: Add
 NL80211_RRF_USER_REGD_NEEDED flag
In-Reply-To: <1448303241-27747-7-git-send-email-sojkam1@fel.cvut.cz>
	(sfid-20151123_192804_844242_D8C85F7B)
References: <1448303241-27747-1-git-send-email-sojkam1@fel.cvut.cz>
	<1448303241-27747-7-git-send-email-sojkam1@fel.cvut.cz>
	(sfid-20151123_192804_844242_D8C85F7B)
Message-ID: <1448613316.2531.13.camel@sipsolutions.net>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Mon, 2015-11-23 at 19:27 +0100, Michal Sojka wrote:
>?
> The NL80211_RRF_USER_REGD_NEEDED flag introduced in this commit
> allows
> drivers to specify that certain band is enabled only if it is
> additionally enabled in user-supplied regulatory database. If the
> band
> is not present there, the channels are simply disabled.

I can see why you'd want this flag internally (although it'll require
rework given the comments on the previous patch) - but is there a
reason to export it in nl80211? Then again, perhaps it *would* be good
to show this information in userspace?

johannes