From: kernel test robot <lkp@intel.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: drivers/power/supply/qcom_battmgr.c:357:31: sparse: sparse: incorrect type in initializer (different base types)
Date: Mon, 28 Aug 2023 06:19:22 +0800 [thread overview]
Message-ID: <202308280602.nE6xa80J-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 85eb043618bb17124050197d71c453d4a1f556e5
commit: 29e8142b5623b5949587bcc4f591c4e6595c4aca power: supply: Introduce Qualcomm PMIC GLINK power supply
date: 7 months ago
config: i386-randconfig-061-20230828 (https://download.01.org/0day-ci/archive/20230828/202308280602.nE6xa80J-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230828/202308280602.nE6xa80J-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308280602.nE6xa80J-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/power/supply/qcom_battmgr.c:357:31: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned int [usertype] battery_id @@ got restricted __le32 [usertype] @@
drivers/power/supply/qcom_battmgr.c:357:31: sparse: expected unsigned int [usertype] battery_id
drivers/power/supply/qcom_battmgr.c:357:31: sparse: got restricted __le32 [usertype]
drivers/power/supply/qcom_battmgr.c:369:31: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned int [usertype] battery_id @@ got restricted __le32 [usertype] @@
drivers/power/supply/qcom_battmgr.c:369:31: sparse: expected unsigned int [usertype] battery_id
drivers/power/supply/qcom_battmgr.c:369:31: sparse: got restricted __le32 [usertype]
>> drivers/power/supply/qcom_battmgr.c:1286:30: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __le32 [usertype] owner @@ got int @@
drivers/power/supply/qcom_battmgr.c:1286:30: sparse: expected restricted __le32 [usertype] owner
drivers/power/supply/qcom_battmgr.c:1286:30: sparse: got int
>> drivers/power/supply/qcom_battmgr.c:1287:29: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __le32 [usertype] type @@ got int @@
drivers/power/supply/qcom_battmgr.c:1287:29: sparse: expected restricted __le32 [usertype] type
drivers/power/supply/qcom_battmgr.c:1287:29: sparse: got int
>> drivers/power/supply/qcom_battmgr.c:1288:31: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __le32 [usertype] opcode @@ got int @@
drivers/power/supply/qcom_battmgr.c:1288:31: sparse: expected restricted __le32 [usertype] opcode
drivers/power/supply/qcom_battmgr.c:1288:31: sparse: got int
vim +357 drivers/power/supply/qcom_battmgr.c
350
351 static int qcom_battmgr_update_status(struct qcom_battmgr *battmgr)
352 {
353 struct qcom_battmgr_update_request request = {
354 .hdr.owner = cpu_to_le32(PMIC_GLINK_OWNER_BATTMGR),
355 .hdr.type = cpu_to_le32(PMIC_GLINK_REQ_RESP),
356 .hdr.opcode = cpu_to_le32(BATTMGR_BAT_STATUS),
> 357 .battery_id = cpu_to_le32(0),
358 };
359
360 return qcom_battmgr_request(battmgr, &request, sizeof(request));
361 }
362
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-27 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 22:19 kernel test robot [this message]
2023-09-13 14:43 ` drivers/power/supply/qcom_battmgr.c:357:31: sparse: sparse: incorrect type in initializer (different base types) Sebastian Reichel
-- strict thread matches above, loose matches on Subject: below --
2023-09-16 13:15 kernel test robot
2023-03-10 17:04 kernel test robot
2023-03-11 17:54 ` [PATCHv1 01/11] dt-bindings: power: supply: adc-battery: add binding Sebastian Reichel
2023-03-12 22:46 ` drivers/power/supply/qcom_battmgr.c:357:31: sparse: sparse: incorrect type in initializer (different base types) Sebastian Reichel
2023-03-04 10:37 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=202308280602.nE6xa80J-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).