The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Geyslan G. Bem" <geyslan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@canonical.com>,
	Peter Senna Tschudin <peter.senna@gmail.com>
Subject: Re: [BUG] checkpatch warning default switch case
Date: Fri, 11 Dec 2015 17:34:54 -0800	[thread overview]
Message-ID: <1449884094.3564.6.camel@perches.com> (raw)
In-Reply-To: <CAGG-pUTh6stPf+DuEjEkMTQSMoOSZ1a02KbpFef8CFG5_5AHHQ@mail.gmail.com>

On Fri, 2015-12-11 at 18:56 -0300, Geyslan G. Bem wrote:
> 2015-12-11 17:21 GMT-03:00 Geyslan G. Bem <geyslan@gmail.com>:
> > 2015-12-11 17:08 GMT-03:00 Joe Perches <joe@perches.com>:
> > > On Fri, 2015-12-11 at 16:34 -0300, Geyslan G. Bem wrote:
> > > > Hello,
> > > > 
> > > > Running
> > > > scripts/checkpatch.pl -f drivers/usb/host/ehci-sched.c
> > > > 
> > > > I got this
> > > > ...
> > > > ERROR: spaces required around that ':' (ctx:VxE)
> > > > #496: FILE: drivers/usb/host/ehci-sched.c:496:
> > > > +                       default:
> > > > ...
> > > > 
> > > > 
> > > > 496:            default:
> > > >                         ehci_dbg (ehci,
> > > >                                 "periodic frame %d bogus type
> > > > %d\n",
> > > >                                 frame, type);
> > > >                 }
> > > > 
> > > > It seems a correct use of default switch case. Maybe the test
> > > > concerns
> > > > to ternary conditional.
> > > > 
> > > > Let me know.
> > > 
> > > Yes, it's a checkpatch defect.
> > > 
> > > It's because a c99 style comment is immediately before this line.
> > > 
> > >         switch (foo) {
> > >         case 1:
> > >                 break;
> > >         // foo
> > >         default:
> > >                 break;
> > >         }
> > > 
> > > emits this ERROR
> > > 
> > > I suggest you fix the comment and the message will go away.
> > Ok, I'm fixing it.
> > 
> > Tks.
> > > 
> > > Andy?  Do you care to fix this defect?
> > > 
> > 
> 
> Another false positive:
> 
> WARNING: braces {} are not necessary for single statement blocks
> #1570: FILE: drivers/usb/host/ehci-sched.c:1570:
> +               else {
> +                       start = (stream->ps.phase << 3) +
> stream->ps.phase_uf;
> +               }
> 
> The code:
> 
>         if (stream->ps.phase == NO_FRAME) {
>             int        done = 0;
> ...
>             reserve_release_iso_bandwidth(ehci, stream, 1);
>         }
> 
>         /* New stream is already scheduled; use the upcoming slot */
>         else {
>             start = (stream->ps.phase << 3) + stream->ps.phase_uf;
>         }
> 
> There's a C89 comment before the else branch and immediately before
> that an empty line. They, I think, are confusing the parser.

checkpatch isn't a real parser

Move the comment into the else block

	if (...) {
		...;
	} else {
		/* New stream ... */
		start = ...;
	}



  reply	other threads:[~2015-12-12  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 19:34 [BUG] checkpatch warning default switch case Geyslan G. Bem
2015-12-11 20:08 ` Joe Perches
2015-12-11 20:21   ` Geyslan G. Bem
2015-12-11 21:56     ` Geyslan G. Bem
2015-12-12  1:34       ` Joe Perches [this message]
2015-12-12  1:51         ` Geyslan G. Bem

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=1449884094.3564.6.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=geyslan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.senna@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