summaryrefslogtreecommitdiff
path: root/drivers/mfd/menf21bmc.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-05-20 12:06:25 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-07-31 08:28:53 +0300
commitbd51cf6997a8cf1a8c122d59ffc541acf5a75f22 (patch)
tree31afe7605fca0e856b88e55da03855e1d51e04d9 /drivers/mfd/menf21bmc.c
parent2ea30596cd7abe27cfb57620be1cd08d87396c45 (diff)
downloadlinux-bd51cf6997a8cf1a8c122d59ffc541acf5a75f22.tar.xz
mfd: arizona: Fix undefined behavior
[ Upstream commit 5da6cbcd2f395981aa9bfc571ace99f1c786c985 ] When the driver is used with a subdevice that is disabled in the kernel configuration, clang gets a little confused about the control flow and fails to notice that n_subdevs is only uninitialized when subdevs is NULL, and we check for that, leading to a false-positive warning: drivers/mfd/arizona-core.c:1423:19: error: variable 'n_subdevs' is uninitialized when used here [-Werror,-Wuninitialized] subdevs, n_subdevs, NULL, 0, NULL); ^~~~~~~~~ drivers/mfd/arizona-core.c:999:15: note: initialize the variable 'n_subdevs' to silence this warning int n_subdevs, ret, i; ^ = 0 Ideally, we would rearrange the code to avoid all those early initializations and have an explicit exit in each disabled case, but it's much easier to chicken out and add one more initialization here to shut up the warning. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Nathan Chancellor <natechancellor@gmail.com> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com> Signed-off-by: Lee Jones <lee.jones@linaro.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/mfd/menf21bmc.c')
0 files changed, 0 insertions, 0 deletions