net: xgene: fix maybe-uninitialized variable
authorArnd Bergmann <arnd@arndb.de>
Tue, 2 Aug 2016 10:23:29 +0000 (12:23 +0200)
committerDavid S. Miller <davem@davemloft.net>
Wed, 3 Aug 2016 18:52:16 +0000 (11:52 -0700)
commitea966cb6b9e11e87f7b146549aef8e13cad5c6ff
treea64fe820180202189b00ba12af2de1b250eb9bb8
parentbce91f8a4247905b8c40a53f72c14db908cd0710
net: xgene: fix maybe-uninitialized variable

Building with -Wmaybe-uninitialized shows a potential use of
an uninitialized variable:

drivers/net/ethernet/apm/xgene/xgene_enet_hw.c: In function 'xgene_enet_phy_connect':
drivers/net/ethernet/apm/xgene/xgene_enet_hw.c:802:23: warning: 'phy_dev' may be used uninitialized in this function [-Wmaybe-uninitialized]

Although the compiler correctly identified this based on the function,
the current code is still safe as long dev->of_node is non-NULL
for the case of CONFIG_ACPI=n, which is currently the case.

The warning is now disabled by default, but still appears when
building with W=1, and other build test tools should be able to
detect it as well. Adding an #else clause here makes the code
more robust and makes it clear to the compiler that this cannot
happen.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 8089a96f601b ("drivers: net: xgene: Add backward compatibility")
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/ethernet/apm/xgene/xgene_enet_hw.c