From: Luis de Bethencourt <luisbg@ubuntu.com>
To: linville@tuxdriver.com, lrodriguez@atheros.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Luis de Bethencourt <luisbg@ubuntu.com>
Subject: [PATCH 2/2] ath: fix macros coding style issue in regd.c
Date: Tue, 30 Mar 2010 00:12:19 +0100 [thread overview]
Message-ID: <1269904339-15599-1-git-send-email-luisbg@ubuntu.com> (raw)
In-Reply-To: <regd.c>
This is a patch to the ath/regd.c file that fixes up three warnings
about macros found by the checkpatch.pl tool, these said that
complex values should be enclosed in parenthesis.
Signed-off-by: Luis de Bethencourt <luisbg@ubuntu.com>
---
drivers/net/wireless/ath/regd.c | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/net/wireless/ath/regd.c b/drivers/net/wireless/ath/regd.c
index 04abd1f..971edc4 100644
--- a/drivers/net/wireless/ath/regd.c
+++ b/drivers/net/wireless/ath/regd.c
@@ -45,15 +45,16 @@
#define ATH9K_5GHZ_5725_5850 REG_RULE(5725-10, 5850+10, 40, 0, 30,\
NL80211_RRF_PASSIVE_SCAN | NL80211_RRF_NO_IBSS)
-#define ATH9K_2GHZ_ALL ATH9K_2GHZ_CH01_11, \
+#define ATH9K_2GHZ_ALL (ATH9K_2GHZ_CH01_11, \
ATH9K_2GHZ_CH12_13, \
- ATH9K_2GHZ_CH14
+ ATH9K_2GHZ_CH14)
+
+#define ATH9K_5GHZ_ALL (ATH9K_5GHZ_5150_5350, \
+ ATH9K_5GHZ_5470_5850)
-#define ATH9K_5GHZ_ALL ATH9K_5GHZ_5150_5350, \
- ATH9K_5GHZ_5470_5850
/* This one skips what we call "mid band" */
-#define ATH9K_5GHZ_NO_MIDBAND ATH9K_5GHZ_5150_5350, \
- ATH9K_5GHZ_5725_5850
+#define ATH9K_5GHZ_NO_MIDBAND (ATH9K_5GHZ_5150_5350, \
+ ATH9K_5GHZ_5725_5850)
/* Can be used for:
* 0x60, 0x61, 0x62 */
--
1.6.3.3
next parent reply other threads:[~2010-03-29 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <regd.c>
2010-03-29 23:12 ` Luis de Bethencourt [this message]
2010-03-29 23:33 ` [PATCH 2/2] ath: fix macros coding style issue in regd.c Joe Perches
[not found] ` <1269905624.4558.56.camel-AkRN8/LKpobuYGix6ZUp1Q@public.gmane.org>
2010-03-29 23:39 ` Luis de Bethencourt
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=1269904339-15599-1-git-send-email-luisbg@ubuntu.com \
--to=luisbg@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=netdev@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).