diff mbox

cfg80211: fix regulatory flags kdoc

Message ID 1384335428-24112-1-git-send-email-mcgrof@do-not-panic.com (mailing list archive)
State Not Applicable, archived
Headers show

Commit Message

Luis R. Rodriguez Nov. 13, 2013, 9:37 a.m. UTC 
Remove the _FLAG prefix as it was not used.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
 include/net/regulatory.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Johannes Berg Nov. 13, 2013, 9:44 a.m. UTC | #1 
On Wed, 2013-11-13 at 10:37 +0100, Luis R. Rodriguez wrote:
> Remove the _FLAG prefix as it was not used.

I'll add this to the right patch

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/include/net/regulatory.h b/include/net/regulatory.h
index 7e98e5a..7e49cf6 100644
--- a/include/net/regulatory.h
+++ b/include/net/regulatory.h
@@ -89,14 +89,14 @@  struct regulatory_request {
 /**
  * enum ieee80211_regulatory_flags - device regulatory flags
  *
- * @REGULATORY_FLAG_CUSTOM_REG: tells us the driver for this device
+ * @REGULATORY_CUSTOM_REG: tells us the driver for this device
  * 	has its own custom regulatory domain and cannot identify the
  * 	ISO / IEC 3166 alpha2 it belongs to. When this is enabled
  * 	we will disregard the first regulatory hint (when the
  * 	initiator is %REGDOM_SET_BY_CORE). Drivers that use
  * 	wiphy_apply_custom_regulatory() should have this flag set
  * 	or the regulatory core will set it for the wiphy.
- * @REGULATORY_FLAG_STRICT_REG: tells us that the wiphy for this device
+ * @REGULATORY_STRICT_REG: tells us that the wiphy for this device
  *	has regulatory domain that it wishes to be considered as the
  *	superset for regulatory rules. After this device gets its regulatory
  *	domain programmed further regulatory hints shall only be considered
@@ -112,7 +112,7 @@  struct regulatory_request {
  *	will have their wiphy->regd programmed once the regulatory
  *	domain is set, and all other regulatory hints will be ignored
  *	until their own regulatory domain gets programmed.
- * @REGULATORY_FLAG_DISABLE_BEACON_HINTS: enable this if your driver needs to
+ * @REGULATORY_DISABLE_BEACON_HINTS: enable this if your driver needs to
  *	ensure that passive scan flags and beaconing flags may not be lifted by
  *	cfg80211 due to regulatory beacon hints. For more information on beacon
  *	hints read the documenation for regulatory_hint_found_beacon()