Message ID | 20220411135440.558394-1-hdegoede@redhat.com (mailing list archive) |
---|---|
State | Accepted |
Commit | b541f9e59a0e56fff840cf983394e59de7bc2d96 |
Headers | show |
Series | phy: ti: tusb1210: Make tusb1210_chg_det_states static | expand |
On 11-04-22, 15:54, Hans de Goede wrote: > Make tusb1210_chg_det_states static, fixing the following sparse warning: > > drivers/phy/ti/phy-tusb1210.c:158:12: sparse: sparse: > symbol 'tusb1210_chg_det_states' was not declared. Should it be static? Applied, thanks
diff --git a/drivers/phy/ti/phy-tusb1210.c b/drivers/phy/ti/phy-tusb1210.c index a0cdbcadf09e..c5bd74874f73 100644 --- a/drivers/phy/ti/phy-tusb1210.c +++ b/drivers/phy/ti/phy-tusb1210.c @@ -155,7 +155,7 @@ static int tusb1210_set_mode(struct phy *phy, enum phy_mode mode, int submode) } #ifdef CONFIG_POWER_SUPPLY -const char * const tusb1210_chg_det_states[] = { +static const char * const tusb1210_chg_det_states[] = { "CHG_DET_CONNECTING", "CHG_DET_START_DET", "CHG_DET_READ_DET",
Make tusb1210_chg_det_states static, fixing the following sparse warning: drivers/phy/ti/phy-tusb1210.c:158:12: sparse: sparse: symbol 'tusb1210_chg_det_states' was not declared. Should it be static? Fixes: 48969a5623ed ("phy: ti: tusb1210: Add charger detection") Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> --- drivers/phy/ti/phy-tusb1210.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)