Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1484557
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] PM / OPP: avoid maybe-uninitialized warning |
| Date | 2016-09-15 23:50 +0200 |
| Message-ID | <shMHD-40l-5@gated-at.bofh.it> (permalink) |
| References | <shGVz-ku-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 09/15/2016 08:38 AM, Arnd Bergmann wrote:
> When CONFIG_OPTIMIZE_INLINING is set and we are building with -Wmaybe-uninitialized
> enabled, we can get a warning for the opp core driver:
>
> drivers/base/power/opp/core.c: In function 'dev_pm_opp_set_rate':
> drivers/base/power/opp/core.c:560:8: warning: 'ou_volt_min' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> This has only now appeared as a result of commit 797da5598f3a ("PM / devfreq:
> Add COMPILE_TEST for build coverage"), which makes the driver visible in
> some configurations that didn't have it before.
>
> The warning is a false positive that I got with gcc-6.1.1, but there is
> a simple workaround in removing the local variables that we get warnings
> for (all three are affected depending on the configuration). This also
> makes the code easier to read.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] PM / OPP: avoid maybe-uninitialized warning Arnd Bergmann <arnd@arndb.de> - 2016-09-15 17:40 +0200 Re: [PATCH] PM / OPP: avoid maybe-uninitialized warning Stephen Boyd <sboyd@codeaurora.org> - 2016-09-15 23:50 +0200 Re: [PATCH] PM / OPP: avoid maybe-uninitialized warning Viresh Kumar <viresh.kumar@linaro.org> - 2016-09-16 05:00 +0200
csiph-web