From: Keerthy <j-keerthy@ti•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Lee Jones <lee.jones@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
<gustavo@embeddedor•com>, <keescook@chromium•org>
Subject: Re: linux-next: build warning after merge of the mfd tree
Date: Thu, 27 Jun 2019 11:29:18 +0530 [thread overview]
Message-ID: <1b5aa183-6e33-ee15-4c65-5b4cdf7655af@ti.com> (raw)
In-Reply-To: <20190627151140.232a87e2@canb.auug.org.au>
On 27/06/19 10:41 AM, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/regulator/lp87565-regulator.c: In function 'lp87565_regulator_probe':
> drivers/regulator/lp87565-regulator.c:182:11: warning: this statement may fall through [-Wimplicit-fallthrough=]
> max_idx = LP87565_BUCK_3210;
Missed adding a break here. Can i send a patch on top of linux-next?
> ~~~~~~~~^~~~~~~~~~~~~~~~~~~
> drivers/regulator/lp87565-regulator.c:183:2: note: here
> default:
> ^~~~~~~
>
> Introduced by commit
>
> 7ee63bd74750 ("regulator: lp87565: Add 4-phase lp87561 regulator support")
>
> 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).
>
next parent reply other threads:[~2019-06-27 5:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190627151140.232a87e2@canb.auug.org.au>
2019-06-27 5:59 ` Keerthy [this message]
2019-07-02 8:49 ` linux-next: build warning after merge of the mfd tree Stephen Rothwell
2019-07-02 11:09 ` Lee Jones
2025-07-24 1:54 Stephen Rothwell
2025-07-24 10:03 ` Lee Jones
2025-07-29 1:35 ` Stephen Rothwell
2025-08-05 3:39 ` Stephen Rothwell
2025-08-05 13:19 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 2:44 Stephen Rothwell
2018-06-05 3:15 Stephen Rothwell
2018-06-05 6:55 ` Lee Jones
2017-11-30 0:35 Stephen Rothwell
2017-11-30 8:28 ` Lee Jones
2017-01-25 4:54 Stephen Rothwell
2017-01-25 8:13 ` Benjamin Gaignard
2013-07-03 5:56 Stephen Rothwell
2013-07-07 18:29 ` Sebastian Andrzej Siewior
2011-12-20 3:11 Stephen Rothwell
2010-11-29 0:52 Stephen Rothwell
2010-11-30 10:02 ` Samuel Ortiz
2010-03-03 5:22 Stephen Rothwell
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=1b5aa183-6e33-ee15-4c65-5b4cdf7655af@ti.com \
--to=j-keerthy@ti$(echo .)com \
--cc=gustavo@embeddedor$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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