From: Joe Perches <joe@perches.com>
To: Cheng-Wei Lee <lee.rhapsody@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sherif Shehab Aldin <shehabaldin.sherif@gmail.com>,
Avinash Kumar <avi.kp.137@gmail.com>,
Peter Senna Tschudin <peter.senna@gmail.com>,
devel <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: wlan-ng/hfa384x_usb.c: add blank line after declarations
Date: Wed, 25 Jun 2014 19:07:24 -0700 [thread overview]
Message-ID: <1403748444.7977.2.camel@joe-AO725> (raw)
In-Reply-To: <CAJKoSVSBBawWBzOmQixTf+DZpWLk1YyNao2-5ESM1-VdTWnFpg@mail.gmail.com>
On Thu, 2014-06-26 at 09:55 +0800, Cheng-Wei Lee wrote:
> This patch fixes the following checkpatch.pl issues in hfa384x_usb.c:
> WARNING: Missing a blank line after declarations
This time you've got the right subject, and right type of content,
but unfortunately, the content is wrapped and can't be applied.
Please read Documentation/email-clients.txt
and resubmit.
> diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c
> b/drivers/staging/wlan-ng/hfa384x_usb.c
> index 98343ff7..07cee56 100644
> --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
> @@ -3705,6 +3705,7 @@ static void hfa384x_usbout_callback(struct urb *urb)
> case -EPIPE:
> {
> hfa384x_t *hw = wlandev->priv;
> +
> netdev_warn(hw->wlandev->netdev,
> "%s tx pipe stalled:
> requesting reset\n",
> wlandev->netdev->name);
> --
next prev parent reply other threads:[~2014-06-26 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 1:55 [PATCH] staging: wlan-ng/hfa384x_usb.c: add blank line after declarations Cheng-Wei Lee
2014-06-26 2:07 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-26 14:43 Cheng-Wei Lee
2014-06-27 1:08 ` Greg Kroah-Hartman
2014-06-27 11:42 Cheng-Wei Lee
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=1403748444.7977.2.camel@joe-AO725 \
--to=joe@perches.com \
--cc=avi.kp.137@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.rhapsody@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.senna@gmail.com \
--cc=shehabaldin.sherif@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