This patch inserts blank lines after declarations to avoid checkpatch
warnings.

After our fixes in 'wlan-ng/prism2sta' there is still a checkpatch
warning about prefering 'ether_addr_copy' instead of 'memcpy'
remaining.

Signed-off-by: Johannes Stadlinger <johannes.stadlin...@fau.de>
Signed-off-by: Maximilian Eschenbacher <maximilian@eschenbacher.email>
CC: linux-ker...@i4.cs.fau.de
CC: Greg Kroah-Hartman <gre...@linuxfoundation.org>
CC: Tugce Sirin <ztugcesi...@gmail.com>
CC: Josh Triplett <j...@joshtriplett.org>
CC: Himangi Saraogi <himangi...@gmail.com>
CC: Paul Gortmaker <paul.gortma...@windriver.com>
CC: Vitaly Osipov <vitaly.osi...@gmail.com>
CC: Neil Armstrong <superna9...@gmail.com>
CC: de...@driverdev.osuosl.org
CC: linux-kernel@vger.kernel.org
---
 drivers/staging/wlan-ng/prism2sta.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/staging/wlan-ng/prism2sta.c 
b/drivers/staging/wlan-ng/prism2sta.c
index 9444006..8d4d7ba 100644
--- a/drivers/staging/wlan-ng/prism2sta.c
+++ b/drivers/staging/wlan-ng/prism2sta.c
@@ -360,6 +360,7 @@ static int prism2sta_mlmerequest(wlandevice_t *wlandev, 
struct p80211msg *msg)
        case DIDmsg_lnxreq_ifstate:
                {
                        struct p80211msg_lnxreq_ifstate *ifstatemsg;
+
                        pr_debug("Received mlme ifstate request\n");
                        ifstatemsg = (struct p80211msg_lnxreq_ifstate *) msg;
                        result =
@@ -1411,6 +1412,7 @@ void prism2sta_processing_defer(struct work_struct *data)
                 */
                if (hw->join_ap && --hw->join_retries > 0) {
                        hfa384x_JoinRequest_data_t joinreq;
+
                        joinreq = hw->joinreq;
                        /* Send the join request */
                        hfa384x_drvr_setconfig(hw,
-- 
1.9.1

--
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