I missed a few redundant newlines the first time.

Signed-off-by: Jesper Juhl <j...@chaosbits.net>
---
 drivers/staging/vt6656/iwctl.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/drivers/staging/vt6656/iwctl.c b/drivers/staging/vt6656/iwctl.c
index 13ad62c..8b9894b 100644
--- a/drivers/staging/vt6656/iwctl.c
+++ b/drivers/staging/vt6656/iwctl.c
@@ -964,7 +964,6 @@ int iwctl_giwrts(struct net_device *dev, struct 
iw_request_info *info,
        wrq->value = pDevice->wRTSThreshold;
        wrq->disabled = (wrq->value >= 2312);
        wrq->fixed = 1;
-
        return 0;
 }
 
@@ -1003,7 +1002,6 @@ int iwctl_giwfrag(struct net_device *dev, struct 
iw_request_info *info,
        wrq->value = pDevice->wFragmentationThreshold;
        wrq->disabled = (wrq->value >= 2312);
        wrq->fixed = 1;
-
        return 0;
 }
 
@@ -1097,7 +1095,6 @@ int iwctl_siwencode(struct net_device *dev, struct 
iw_request_info *info,
 
        // Send the key to the card
        if (wrq->length > 0) {
-
                if (wrq->length == WLAN_WEP232_KEYLEN) {
                        DBG_PRT(MSG_LEVEL_DEBUG, KERN_INFO "Set 232 bit wep 
key\n");
                } else if (wrq->length == WLAN_WEP104_KEYLEN) {
@@ -1119,8 +1116,7 @@ int iwctl_siwencode(struct net_device *dev, struct 
iw_request_info *info,
                                        dwKeyIndex | (1 << 31),
                                        wrq->length, NULL,
                                        pDevice->abyKey,
-                                       KEY_CTL_WEP
-                               );
+                                       KEY_CTL_WEP);
                        spin_unlock_irq(&pDevice->lock);
                }
                pDevice->byKeyIndex = (BYTE)dwKeyIndex;
-- 
1.7.11.1


-- 
Jesper Juhl <j...@chaosbits.net>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to