[PATCH] staging: csr: fix coding style
From: SeongJae Park
Date: Mon Oct 15 2012 - 03:56:02 EST
Fix coding style of csr_framework_ext_types.h
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
drivers/staging/csr/csr_framework_ext_types.h | 33 +++++++++++--------------
1 file changed, 15 insertions(+), 18 deletions(-)
diff --git a/drivers/staging/csr/csr_framework_ext_types.h b/drivers/staging/csr/csr_framework_ext_types.h
index 57194ee..7e9cf8e 100644
--- a/drivers/staging/csr/csr_framework_ext_types.h
+++ b/drivers/staging/csr/csr_framework_ext_types.h
@@ -2,11 +2,11 @@
#define CSR_FRAMEWORK_EXT_TYPES_H__
/*****************************************************************************
- (c) Cambridge Silicon Radio Limited 2010
- All rights reserved and confidential information of CSR
+ (c) Cambridge Silicon Radio Limited 2010
+ All rights reserved and confidential information of CSR
- Refer to LICENSE.txt included with this source for details
- on the license terms.
+ Refer to LICENSE.txt included with this source for details
+ on the license terms.
*****************************************************************************/
@@ -24,17 +24,15 @@ extern "C" {
#ifdef __KERNEL__
-struct CsrThread
-{
- struct task_struct *thread_task;
- char name[16];
+struct CsrThreadi {
+ struct task_struct *thread_task;
+ char name[16];
};
-struct CsrEvent
-{
- /* wait_queue for waking the kernel thread */
- wait_queue_head_t wakeup_q;
- unsigned int wakeup_flag;
+struct CsrEvent {
+ /* wait_queue for waking the kernel thread */
+ wait_queue_head_t wakeup_q;
+ unsigned int wakeup_flag;
};
typedef struct CsrEvent CsrEventHandle;
@@ -43,11 +41,10 @@ typedef struct CsrThread CsrThreadHandle;
#else /* __KERNEL __ */
-struct CsrEvent
-{
- pthread_cond_t event;
- pthread_mutex_t mutex;
- u32 eventBits;
+struct CsrEvent {
+ pthread_cond_t event;
+ pthread_mutex_t mutex;
+ u32 eventBits;
};
typedef struct CsrEvent CsrEventHandle;
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/