From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Joe Perches <joe@perches.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH][next] Input: Fix fall-through warning for Clang
Date: Tue, 29 Jun 2021 09:05:25 -0500 [thread overview]
Message-ID: <20210629140525.GA65130@embeddedor> (raw)
In-Reply-To: <YMfUT7pvBWreiR1K@google.com>
On Mon, Jun 14, 2021 at 03:12:31PM -0700, Dmitry Torokhov wrote:
> Hi Joe,
>
> On Mon, Jun 07, 2021 at 03:02:40PM -0700, Joe Perches wrote:
> > On Mon, 2021-06-07 at 16:48 -0500, Gustavo A. R. Silva wrote:
> > > In preparation to enable -Wimplicit-fallthrough for Clang, fix a
> > > warning by explicitly adding a fallthrough; statement.
> > []
> > > diff --git a/drivers/input/joystick/sidewinder.c b/drivers/input/joystick/sidewinder.c
> > []
> > > @@ -660,6 +660,7 @@ static int sw_connect(struct gameport *gameport, struct gameport_driver *drv)
> > > fallthrough;
> > > case 45: /* Ambiguous packet length */
> > > if (j <= 40) { /* ID length less or eq 40 -> FSP */
> > > + fallthrough;
> > > case 43:
> > > sw->type = SW_ID_FSP;
> > > break;
> >
> > Yuck. Super ugly. There's no need to play games with indentation.
>
> Yeah, the original code is not pretty :(
Isn't this a Duff device for performance[1]?
In which case it might be better not to modify it and just go
with the fallthrough marking?
Another similar case can be found at
drivers/scsi/aic94xx/aic94xx_sds.c:714:
714 static void *asd_find_ll_by_id(void * const start, const u8 id0, const u8 id1)
715 {
716 struct asd_ll_el *el = start;
717
718 do {
719 switch (id1) {
720 default:
721 if (el->id1 == id1)
722 case 0xFF:
723 if (el->id0 == id0)
724 return el;
725 }
726 el = start + le16_to_cpu(el->next);
727 } while (el != start);
728
729 return NULL;
730 }
--
Gustavo
[1] https://www.drdobbs.com/a-reusable-duff-device/184406208
>
> >
> > Perhaps the simpler:
> >
> > case 43:
> > sw->type = SW_ID_FSP;
> > break;
> > case 45: /* Ambiguous packet length */
> > if (j <= 40) { /* ID length less or eq 40 -> FSP */
> > sw->type = SW_ID_FSP;
> > break;
> > }
> > sw->number++;
> > fallthrough;
> >
> >
>
> Could you resubmit this version properly formatted?
>
> Thanks.
>
> --
> Dmitry
prev parent reply other threads:[~2021-06-29 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 21:48 [PATCH][next] Input: Fix fall-through warning for Clang Gustavo A. R. Silva
2021-06-07 22:02 ` Joe Perches
2021-06-14 22:12 ` Dmitry Torokhov
2021-06-29 14:05 ` Gustavo A. R. Silva [this message]
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=20210629140525.GA65130@embeddedor \
--to=gustavoars@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.