From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro•org>,
Zhang Rui <rui.zhang@intel•com>,
Eduardo Valentin <edubezval@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Amit Kucheria <amit.kucheria@linaro•org>
Subject: linux-next: build warning after merge of the thermal tree
Date: Tue, 22 Oct 2019 10:23:34 +1100 [thread overview]
Message-ID: <20191022102334.67e5d3d1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Hi all,
After merging the thermal tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from drivers/thermal/qcom/tsens-common.c:13:
drivers/thermal/qcom/tsens-common.c: In function 'tsens_set_interrupt':
include/linux/regmap.h:87:2: warning: 'index' may be used uninitialized in this function [-Wmaybe-uninitialized]
87 | regmap_field_update_bits_base(field, ~0, val, NULL, false, false)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/thermal/qcom/tsens-common.c:183:6: note: 'index' was declared here
183 | u32 index;
| ^~~~~
In file included from drivers/thermal/qcom/tsens-common.c:13:
include/linux/regmap.h:87:2: warning: 'index_clear' may be used uninitialized in this function [-Wmaybe-uninitialized]
87 | regmap_field_update_bits_base(field, ~0, val, NULL, false, false)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/thermal/qcom/tsens-common.c:199:18: note: 'index_clear' was declared here
199 | u32 index_mask, index_clear;
| ^~~~~~~~~~~
drivers/thermal/qcom/tsens-common.c:199:6: warning: 'index_mask' may be used uninitialized in this function [-Wmaybe-uninitialized]
199 | u32 index_mask, index_clear;
| ^~~~~~~~~~
Introduced by commit
fbfe1a042cfd ("drivers: thermal: tsens: Add interrupt support")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-10-21 23:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 23:23 Stephen Rothwell [this message]
2019-10-22 9:50 ` linux-next: build warning after merge of the thermal tree Amit Kucheria
2019-10-22 11:18 ` Stephen Rothwell
2019-10-24 7:26 ` Amit Kucheria
2019-10-29 9:05 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 9:07 Stephen Rothwell
2020-10-27 0:34 Stephen Rothwell
2020-03-02 23:42 Stephen Rothwell
2020-03-03 0:17 ` Daniel Lezcano
2019-04-30 3:48 Stephen Rothwell
2017-09-01 0:52 Stephen Rothwell
2016-08-24 3:38 Stephen Rothwell
2016-08-24 7:56 ` Zhang Rui
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=20191022102334.67e5d3d1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=amit.kucheria@linaro$(echo .)org \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=edubezval@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rui.zhang@intel$(echo .)com \
/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