From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: David Sterba <dsterba@suse.cz>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch v2] checkpatch: complain about GW-BASIC style label names
Date: Wed, 13 May 2015 14:49:37 +0100 [thread overview]
Message-ID: <20150513144937.67e7e383@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20150513131613.GI23255@twin.jikos.cz>
On Wed, 13 May 2015 15:16:13 +0200
David Sterba <dsterba@suse.cz> wrote:
> On Wed, May 13, 2015 at 03:37:12PM +0300, Dan Carpenter wrote:
> > GW-BASIC style label names are annoying so we can warn about that in
> > checkpatch. The warnings look like:
> >
> > WARNING: 'fail2' isn't informative - prefer descriptive label names
> > #267: FILE: ./sound/ppc/beep.c:267:
> > + fail2: snd_ctl_remove(chip->card, beep_ctl);
> >
> > This generates slightly under 2000 new warnings. None of them are
> > false positives.
>
> Please whitelist fs/btrfs/* from this type of checkpatch warning.
If you could whitelist the rest of the kernel too that would also be
useful.
There's nothing wrong with driver code that ends
fail_3:
xxx
fail_2:
yyy
fail_1:
blah
return;
if anything it makes it very clear which level of unravelling on error is
occurring and at a glance enables you to see that the error handling is
ordered properly.
next prev parent reply other threads:[~2015-05-13 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 11:21 [patch] " Dan Carpenter
2015-05-07 13:47 ` Joe Perches
2015-05-07 19:42 ` Dan Carpenter
2015-05-07 20:17 ` Joe Perches
2015-05-07 20:35 ` Joe Perches
2015-05-13 12:37 ` [patch v2] " Dan Carpenter
2015-05-13 13:16 ` David Sterba
2015-05-13 13:47 ` Dan Carpenter
2015-05-13 13:49 ` One Thousand Gnomes [this message]
2015-06-04 10:46 ` Dan Carpenter
2015-05-13 14:12 ` Al Viro
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=20150513144937.67e7e383@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=apw@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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®