From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Kees Cook <keescook@chromium.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: linux-next: build warning after merge of the input-current tree
Date: Wed, 24 Jul 2019 12:48:21 +0800 [thread overview]
Message-ID: <5463D761-FAFB-4BBE-8EE1-95EF1A52F927@canonical.com> (raw)
In-Reply-To: <20190724095416.65450cbf@canb.auug.org.au>
Hi Stephen,
at 07:54, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the input-current tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/input/mouse/elantech.c: In function 'elantech_use_host_notify':
> drivers/input/mouse/elantech.c:1843:6: warning: this statement may fall
> through [-Wimplicit-fallthrough=]
> if (dmi_get_bios_year() >= 2018)
> ^
> drivers/input/mouse/elantech.c:1845:2: note: here
> default:
> ^~~~~~~
>
> Introduced by commit
>
> 883a2a80f79c ("Input: elantech - enable SMBus on new (2018+) systems")
>
> I get these warnings because I am building with -Wimplicit-fallthrough
> in attempt to catch new additions early. The gcc warning can be turned
> off by adding a /* fall through */ comment at the point the fall through
> happens (assuming that the fall through is intentional).
Yes the fall through is intentional.
Kai-Heng
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2019-07-24 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 23:54 Stephen Rothwell
2019-07-24 4:48 ` Kai-Heng Feng [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=5463D761-FAFB-4BBE-8EE1-95EF1A52F927@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®