From: Sangho Yi <antiroot@gmail.com>
To: devel@driverdev.osuosl.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Sangho Yi <antiroot@gmail.com>
Subject: [PATCH 2/2] staging: csr: Fixed macro definition style errors on csr_wifi_vif_utils.h
Date: Wed, 17 Oct 2012 01:48:30 +0900 [thread overview]
Message-ID: <1350406110-2942-2-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <1350406110-2942-1-git-send-email-antiroot@gmail.com>
I fixed 3 lines of code where there were the coding style errors on
defining the macros.
Signed-off-by: Sangho Yi <antiroot@gmail.com>
---
drivers/staging/csr/csr_wifi_vif_utils.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/csr/csr_wifi_vif_utils.h b/drivers/staging/csr/csr_wifi_vif_utils.h
index c997398..f1374f2 100644
--- a/drivers/staging/csr/csr_wifi_vif_utils.h
+++ b/drivers/staging/csr/csr_wifi_vif_utils.h
@@ -25,8 +25,8 @@ extern "C" {
/* Common macros for NME and SME to be used temporarily until SoftMAC
* changes are made */
-#define CSR_WIFI_NUM_INTERFACES (u8)0x1
-#define CSR_WIFI_INTERFACE_IN_USE (u16)0x0
+#define CSR_WIFI_NUM_INTERFACES ((u8)0x1)
+#define CSR_WIFI_INTERFACE_IN_USE ((u16)0x0)
/* This is used at places where interface Id isn't available*/
#define CSR_WIFI_INTERFACE_ZERO 0
@@ -38,7 +38,7 @@ extern "C" {
/* Extract the Interface Id from the event */
#define CsrWifiVifUtilsGetVifTagFromEvent(msg) \
- ((u16) * ((u16 *) ((u8 *) (msg) + sizeof(CsrWifiFsmEvent))))
+ ((u16) *((u16 *) ((u8 *) (msg) + sizeof(CsrWifiFsmEvent))))
/* The HPI Vif combines the type and the interface id */
#define CsrWifiVifUtilsGetVifTagFromHipEvent(msg) \
--
1.7.9.5
next prev parent reply other threads:[~2012-10-16 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 16:48 [PATCH 1/2] staging: csr: Fixed indentation " Sangho Yi
2012-10-16 16:48 ` Sangho Yi [this message]
2012-10-22 21:07 ` Greg KH
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=1350406110-2942-2-git-send-email-antiroot@gmail.com \
--to=antiroot@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
Powered by JetHome