From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Martyn Welch <martyn.welch@collabora.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: linux-next: build warning after merge of the staging tree
Date: Wed, 14 Aug 2019 09:42:59 +0200 [thread overview]
Message-ID: <20190814074259.GA3495@kroah.com> (raw)
In-Reply-To: <20190814160835.4aabb60a@canb.auug.org.au>
On Wed, Aug 14, 2019 at 04:08:35PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/iio/light/noa1305.c: In function 'noa1305_scale':
> drivers/iio/light/noa1305.c:87:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
> *val2 = 77 * 4;
> ~~~~~~^~~~~~~~
> drivers/iio/light/noa1305.c:88:2: note: here
> case NOA1305_INTEGR_TIME_200MS:
> ^~~~
>
> Introduced by commit
>
> 741172d18e8a ("iio: light: noa1305: Add support for NOA1305")
Fix for this is already in my testing tree, forgot to push it to my
-next branch, but have done so now, thanks!
greg k-h
next prev parent reply other threads:[~2019-08-14 7:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 6:08 linux-next: build warning after merge of the staging tree Stephen Rothwell
2019-08-14 7:42 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 7:16 Stephen Rothwell
2020-09-09 7:41 ` Greg KH
2019-12-13 1:10 Stephen Rothwell
2019-08-26 6:24 Stephen Rothwell
2019-08-26 6:30 ` Greg KH
2019-08-26 8:38 ` Gao Xiang
2019-08-26 8:54 ` Gao Xiang
2019-08-26 9:43 ` Gao Xiang
2019-08-26 9:53 ` Gao Xiang
2019-08-26 11:13 ` Gao Xiang
2019-04-23 5:13 Stephen Rothwell
2018-11-08 2:33 Stephen Rothwell
2018-11-08 11:17 ` Greg KH
2018-09-03 2:06 Stephen Rothwell
2018-09-04 9:04 ` John Whitmore
2018-05-14 4:37 Stephen Rothwell
2018-01-16 2:45 Stephen Rothwell
2018-01-16 5:59 ` Greg KH
2018-01-16 10:47 ` Arnd Bergmann
2018-01-16 15:02 ` Greg KH
2017-01-20 4:36 Stephen Rothwell
2017-01-20 8:37 ` Greg KH
2017-01-20 9:18 ` Linus Walleij
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=20190814074259.GA3495@kroah.com \
--to=greg@kroah.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--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;
as well as URLs for NNTP newsgroup(s).