From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Cheng-Wei Lee <lee.rhapsody@gmail.com>,
Sherif Shehab Aldin <shehabaldin.sherif@gmail.com>,
Avinash Kumar <avi.kp.137@gmail.com>,
Peter Senna Tschudin <peter.senna@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wlan-ng: fix Missing a blank line after declarations warnings
Date: Fri, 13 Jun 2014 10:37:20 -0700 [thread overview]
Message-ID: <1402681040.3509.11.camel@joe-AO725> (raw)
In-Reply-To: <20140613171526.GA19285@kroah.com>
On Fri, 2014-06-13 at 10:15 -0700, Greg Kroah-Hartman wrote:
> On Fri, Jun 13, 2014 at 10:58:14PM +0800, Cheng-Wei Lee wrote:
> > Signed-off-by: Quentin Lee <lee.rhapsody@gmail.com>
[]
> > diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c
[]
> > @@ -3533,7 +3533,6 @@ static void hfa384x_usbin_rx(wlandevice_t
> > *wlandev, struct sk_buff *skb)
> > }
> >
> > done:
> > - return;
> > }
>
> That's a good thing to do, but it is not what you said you did up above
> in the changelog entry.
I don't believe it's a good thing to do at all.
I suspect more that this wasn't compile tested.
This doesn't compile for at least several
supported gcc versions.
gcc doesn't (didn't? I haven't tried 4.9) like:
label:
}
to terminate a function definition.
$ cat label_test.c
void func(void)
{
goto label;
label:
}
$
with gcc 4.8:
$ gcc label_test.c
label_test.c: In function ‘func’:
label_test.c:5:1: error: label at end of compound statement
label:
^
whereas this compiles fine:
$ cat label_test2.c
void func(void)
{
goto label;
label:
;
}
$
next prev parent reply other threads:[~2014-06-13 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 14:58 Cheng-Wei Lee
2014-06-13 17:15 ` Greg Kroah-Hartman
2014-06-13 17:37 ` Joe Perches [this message]
2014-06-16 8:02 ` Dan Carpenter
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=1402681040.3509.11.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
all inboxes | Powered by JetHome®