From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [linusw-nomadik:ux500-href-charging-v5.17-rc1 28/30] drivers/power/supply/samsung-sdi-battery.c:29:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb_l1m7flu' was not declared. Should it be static?
Date: Sat, 26 Feb 2022 02:34:14 +0800 [thread overview]
Message-ID: <202202260125.d751ECgs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git ux500-href-charging-v5.17-rc1
head: ff2a9483749f5860407c6fb4798202b774978a81
commit: 77f450def23a94bcdea9a60f4df683461899158e [28/30] power: supply: Static data for Samsung batteries
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220226/202202260125.d751ECgs-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?id=77f450def23a94bcdea9a60f4df683461899158e
git remote add linusw-nomadik https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git
git fetch --no-tags linusw-nomadik ux500-href-charging-v5.17-rc1
git checkout 77f450def23a94bcdea9a60f4df683461899158e
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/power/supply/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/power/supply/samsung-sdi-battery.c:29:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb_l1m7flu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:57:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb_l1m7flu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:77:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb425161la' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:109:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb425161la' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:186:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb425161lu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:218:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb425161lu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:248:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb485159lu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:275:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb485159lu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:295:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb535151vu' was not declared. Should it be static?
>> drivers/power/supply/samsung-sdi-battery.c:315:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb535151vu' was not declared. Should it be static?
drivers/power/supply/samsung-sdi-battery.c:335:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb585157lu' was not declared. Should it be static?
drivers/power/supply/samsung-sdi-battery.c:405:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb585157lu' was not declared. Should it be static?
drivers/power/supply/samsung-sdi-battery.c:617:46: sparse: sparse: symbol 'samsung_maint_charge_table' was not declared. Should it be static?
drivers/power/supply/samsung-sdi-battery.c:632:28: sparse: sparse: symbol 'samsung_sdi_batteries' 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-02-25 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 18:34 kernel test robot [this message]
2022-02-25 17:44 ` [RFC PATCH linusw-nomadik] power: supply: samsung_vbat2res_discharging_eb_l1m7flu[] can be static kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202202260125.d751ECgs-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.