mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yan Laijun <yan.laijun@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	Bhumika Goyal <bhumirks@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] staging: wlan-ng: Fixed too long code line warnings.
Date: Fri, 2 Dec 2016 18:09:16 +0800	[thread overview]
Message-ID: <6d37d427c3203961e7f3f0020d2b971d92e7b52c.1480671565.git.yan.laijun@gmail.com> (raw)
In-Reply-To: <cover.1480671565.git.yan.laijun@gmail.com>

Fixed checkpatch warning "line over 80 characters" in
wlan-ng/hfa384x_usb.c file.

Signed-off-by: Yan Laijun <yan.laijun@gmail.com>
---
Changes in v2:
  - Remove initialization of usbin on its decarlation.
---
 drivers/staging/wlan-ng/hfa384x_usb.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
index 5f11f6e..c7bda04 100644
--- a/drivers/staging/wlan-ng/hfa384x_usb.c
+++ b/drivers/staging/wlan-ng/hfa384x_usb.c
@@ -3037,7 +3037,7 @@ static void hfa384x_usbin_callback(struct urb *urb)
 {
 	struct wlandevice *wlandev = urb->context;
 	struct hfa384x *hw;
-	union hfa384x_usbin *usbin = (union hfa384x_usbin *)urb->transfer_buffer;
+	union hfa384x_usbin *usbin;
 	struct sk_buff *skb = NULL;
 	int result;
 	int urb_status;
@@ -3049,6 +3049,7 @@ static void hfa384x_usbin_callback(struct urb *urb)
 		ABORT
 	} action;
 
+	usbin = (union hfa384x_usbin *)urb->transfer_buffer;
 	if (!wlandev || !wlandev->netdev || wlandev->hwremoved)
 		goto exit;
 
-- 
1.9.1

  reply	other threads:[~2016-12-02 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30  4:29 [PATCH] Staging: wlan-ng: hfa384x_usb.c " Yan Laijun
2016-11-30  9:01 ` Greg KH
2016-12-02 10:08   ` Yan Laijun
2016-12-02 10:09     ` Yan Laijun [this message]
2016-12-02 10:49       ` [PATCH v2] staging: wlan-ng: " Markus Böhme

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=6d37d427c3203961e7f3f0020d2b971d92e7b52c.1480671565.git.yan.laijun@gmail.com \
    --to=yan.laijun@gmail.com \
    --cc=bhumirks@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®