From patchwork Wed Nov 13 09:37:08 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Luis R. Rodriguez" X-Patchwork-Id: 3177761 Return-Path: X-Original-To: patchwork-linux-wireless@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 1FA09C045B for ; Wed, 13 Nov 2013 09:37:23 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 01E6E2010E for ; Wed, 13 Nov 2013 09:37:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 48CF0200FE for ; Wed, 13 Nov 2013 09:37:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759067Ab3KMJhO (ORCPT ); Wed, 13 Nov 2013 04:37:14 -0500 Received: from mail-bk0-f43.google.com ([209.85.214.43]:53815 "EHLO mail-bk0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758798Ab3KMJhM (ORCPT ); Wed, 13 Nov 2013 04:37:12 -0500 Received: by mail-bk0-f43.google.com with SMTP id mz13so190758bkb.2 for ; Wed, 13 Nov 2013 01:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:date:message-id; bh=JXs7T9gZQhvzAXur6zWZZMXcfgGgjHsF/qMQRDlMwGw=; b=wz2xjYhgnugOhjKmxTPSGK+RL3fDB+MUvhKw1oR7YbeC7WJjIe34L7ixO7RmiaQUPz aNqaTZn1rJ5/JcXw875GcukZoUXXHqz9xMzyHbI/ZYCkDeksS4jItgVb3Th1Khw145/K LdgrgN52S4tM7MMstMwpeniit+3bljT2SsPDv1udn5styTmnmttBDwQXG63yqNzAd+tw 7HYGihS0OIT1SUOgUairS1CAXB7T5IyxyXfK10Q7h04ceSfpl8ypW8V/ZxSPY96M4ASe XpDtxCihd8p5DTbzsOnoH1NBEEGb215NYJ3qRk1Yu6Mj54jc3/hiz5wTPptczNU717MB CfXQ== X-Received: by 10.204.167.72 with SMTP id p8mr570720bky.54.1384335431316; Wed, 13 Nov 2013 01:37:11 -0800 (PST) Received: from mcgrof@gmail.com (thinkpad-luis.rsr.lip6.fr. [132.227.76.46]) by mx.google.com with ESMTPSA id on10sm21608627bkb.13.2013.11.13.01.37.09 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 13 Nov 2013 01:37:10 -0800 (PST) Received: by mcgrof@gmail.com (sSMTP sendmail emulation); Wed, 13 Nov 2013 10:37:09 +0100 From: "Luis R. Rodriguez" To: johannes@sipsolutions.net Cc: linux-wireless@vger.kernel.org, "Luis R. Rodriguez" Subject: [PATCH] cfg80211: fix regulatory flags kdoc Date: Wed, 13 Nov 2013 10:37:08 +0100 Message-Id: <1384335428-24112-1-git-send-email-mcgrof@do-not-panic.com> X-Mailer: git-send-email 1.8.4.rc3 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Remove the _FLAG prefix as it was not used. Signed-off-by: Luis R. Rodriguez --- include/net/regulatory.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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()