[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201904160046.ggavw2OV%lkp@intel.com>
Date: Tue, 16 Apr 2019 00:52:38 +0800
From: kbuild test robot <lkp@...el.com>
To: Pascal PAILLET-LME <p.paillet@...com>
Cc: kbuild-all@...org, Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org
Subject: [regulator:for-next 103/105] drivers/regulator/stm32-pwr.c:35:5:
sparse: symbol 'ready_mask_table' was not declared. Should it be static?
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
head: 598387d3ce4bd982272a2bc990dfad6d67d20efd
commit: 6cdae8173f6771977c3863bac7f1455c96bb1f6e [103/105] regulator: Add support for stm32 power regulators
reproduce:
# apt-get install sparse
git checkout 6cdae8173f6771977c3863bac7f1455c96bb1f6e
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:47:5: sparse: symbol 'stm32_pwr_reg_is_ready' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:57:5: sparse: symbol 'stm32_pwr_reg_is_enabled' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists