[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <202005301757.zXvAYTUt%lkp@intel.com>
Date: Sat, 30 May 2020 17:39:51 +0800
From: kbuild test robot <lkp@...el.com>
To: "Jonathan, Bakker," <xc-racer2@...e.ca>
Cc: kbuild-all@...ts.01.org, Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: [regulator:for-5.8 14/18] drivers/regulator/max8998.c:418:5: sparse:
sparse: symbol 'max8998_get_current_limit' was not declared. Should it be
static?
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.8
head: 81227f49bd272cbcd9bb4650b250519c8aa22065
commit: 4ffea5e083f8125fe273cf331ecb10d901eb64a2 [14/18] regulator: max8998: Add charger regulator
config: x86_64-randconfig-s021-20200529 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-243-gc100a7ab-dirty
git checkout 4ffea5e083f8125fe273cf331ecb10d901eb64a2
# save the attached .config to linux build tree
make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@...el.com>
sparse warnings: (new ones prefixed by >>)
drivers/regulator/max8998.c:374:5: sparse: sparse: symbol 'max8998_set_current_limit' was not declared. Should it be static?
>> drivers/regulator/max8998.c:418:5: sparse: sparse: symbol 'max8998_get_current_limit' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Download attachment ".config.gz" of type "application/gzip" (36703 bytes)
Powered by blists - more mailing lists