From: Harsh Kumar <harsh1kumar@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [Patch 2/2] Staging: winbond: Removed undesired spaces, lines and tabs
Date: Wed, 26 Sep 2012 05:45:15 +0000 [thread overview]
Message-ID: <5062939B.1030906@gmail.com> (raw)
checkpatch cleanup: Removed some undesired spaces, lines and tabs to comply with coding style.
Signed-off-by: Harsh Kumar <harsh1kumar@gmail.com>
diff -uprN a/drivers/staging/winbond/wb35tx_s.h b/drivers/staging/winbond/wb35tx_s.h
--- a/drivers/staging/winbond/wb35tx_s.h
+++ b/drivers/staging/winbond/wb35tx_s.h
@@ -4,16 +4,12 @@
#include "mds_s.h"
/* IS89C35 Tx related definition */
-#define TX_INTERFACE 0 /* Interface 1 */
-#define TX_PIPE 3 /* Endpoint 4 */
-#define TX_INTERRUPT 1 /* Endpoint 2 */
+#define TX_INTERFACE 0 /* Interface 1 */
+#define TX_PIPE 3 /* Endpoint 4 */
+#define TX_INTERRUPT 1 /* Endpoint 2 */
#define MAX_INTERRUPT_LENGTH 64 /* It must be 64 for EP2 hardware */
-
-
/* Internal variable for module */
-
-
struct wb35_tx {
/* For Tx buffer */
u8 TxBuffer[ MAX_USB_TX_BUFFER_NUMBER ][ MAX_USB_TX_BUFFER ];
@@ -23,15 +19,15 @@ struct wb35_tx {
atomic_t TxResultCount; /* For thread control of EP2 931130.4.m */
atomic_t TxFireCounter; /* For thread control of EP4 931130.4.n */
- u32 ByteTransfer;
+ u32 ByteTransfer;
- u32 TxSendIndex; /* The next index of Mds array to be sent */
- u32 EP2vm_state; /* for EP2vm state */
- u32 EP4vm_state; /* for EP4vm state */
- u32 tx_halt; /* Stopping VM */
+ u32 TxSendIndex; /* The next index of Mds array to be sent */
+ u32 EP2vm_state; /* for EP2vm state */
+ u32 EP4vm_state; /* for EP4vm state */
+ u32 tx_halt; /* Stopping VM */
- struct urb * Tx4Urb;
- struct urb * Tx2Urb;
+ struct urb *Tx4Urb;
+ struct urb *Tx2Urb;
int EP2VM_status;
int EP4VM_status;
next reply other threads:[~2012-09-26 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 5:45 Harsh Kumar [this message]
2012-09-26 6:37 ` [Patch 2/2] Staging: winbond: Removed undesired spaces, lines and tabs Dan Carpenter
2012-09-26 11:36 ` Pavel Machek
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=5062939B.1030906@gmail.com \
--to=harsh1kumar@gmail.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.