This patch removes redundant goto or break statements in hfa384x_usb.c as found 
by checkpatch.pl

Signed-off-by: Ilja Sidoroff <[email protected]>
---
Changes in v2:
   * replaced goto with break and so got rid of a label

 drivers/staging/wlan-ng/hfa384x_usb.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c 
b/drivers/staging/wlan-ng/hfa384x_usb.c
index 2f63e0c..cac55c6 100644
--- a/drivers/staging/wlan-ng/hfa384x_usb.c
+++ b/drivers/staging/wlan-ng/hfa384x_usb.c
@@ -3474,7 +3474,7 @@ static void hfa384x_usbin_rx(wlandevice_t *wlandev, 
struct sk_buff *skb)
                /* If exclude and we receive an unencrypted, drop it */
                if ((wlandev->hostwep & HOSTWEP_EXCLUDEUNENCRYPTED) &&
                    !WLAN_GET_FC_ISWEP(fc)) {
-                       goto done;
+                       break;
                }
 
                data_len = le16_to_cpu(usbin->rxfrm.desc.data_len);
@@ -3528,11 +3528,9 @@ static void hfa384x_usbin_rx(wlandevice_t *wlandev, 
struct sk_buff *skb)
                netdev_warn(hw->wlandev->netdev, "Received frame on unsupported 
port=%d\n",
                            HFA384x_RXSTATUS_MACPORT_GET(
                                    usbin->rxfrm.desc.status));
-               goto done;
                break;
        }
 
-done:
        return;
 }
 
@@ -4127,7 +4125,6 @@ static int hfa384x_isgood_pdrcode(u16 pdrcode)
        case HFA384x_PDR_HFA3861_MANF_TESTI:
                /* code is OK */
                return 1;
-               break;
        default:
                if (pdrcode < 0x1000) {
                        /* code is OK, but we don't know exactly what it is */
@@ -4140,7 +4137,6 @@ static int hfa384x_isgood_pdrcode(u16 pdrcode)
                                 pdrcode);
                        return 0;
                }
-               break;
        }
        return 0;               /* avoid compiler warnings */
 }
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
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