linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: [linux-next:master 939/4884] drivers/soc/qcom/pmic_pdcharger_ulog.c:57:34: sparse: sparse: incorrect type in initializer (different base types)
Date: Wed, 6 Dec 2023 03:46:31 +0800	[thread overview]
Message-ID: <202312060355.M0eJtq4X-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   0f5f12ac05f36f117e793656c3f560625e927f1b
commit: 086fdb48bc65d6fde0f0e7d42dbfb3c00ea52628 [939/4884] soc: qcom: add ADSP PDCharger ULOG driver
config: i386-randconfig-061-20231206 (https://download.01.org/0day-ci/archive/20231206/202312060355.M0eJtq4X-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312060355.M0eJtq4X-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/202312060355.M0eJtq4X-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/soc/qcom/pmic_pdcharger_ulog.c:57:34: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le32 [usertype] owner @@     got int @@
   drivers/soc/qcom/pmic_pdcharger_ulog.c:57:34: sparse:     expected restricted __le32 [usertype] owner
   drivers/soc/qcom/pmic_pdcharger_ulog.c:57:34: sparse:     got int
>> drivers/soc/qcom/pmic_pdcharger_ulog.c:58:33: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le32 [usertype] type @@     got int @@
   drivers/soc/qcom/pmic_pdcharger_ulog.c:58:33: sparse:     expected restricted __le32 [usertype] type
   drivers/soc/qcom/pmic_pdcharger_ulog.c:58:33: sparse:     got int
>> drivers/soc/qcom/pmic_pdcharger_ulog.c:59:35: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le32 [usertype] opcode @@     got int @@
   drivers/soc/qcom/pmic_pdcharger_ulog.c:59:35: sparse:     expected restricted __le32 [usertype] opcode
   drivers/soc/qcom/pmic_pdcharger_ulog.c:59:35: sparse:     got int

vim +57 drivers/soc/qcom/pmic_pdcharger_ulog.c

    52	
    53	static int pmic_pdcharger_ulog_request(struct pmic_pdcharger_ulog *pg)
    54	{
    55		struct get_ulog_req_msg req_msg = {
    56			.hdr = {
  > 57				.owner = MSG_OWNER_CHG_ULOG,
  > 58				.type = MSG_TYPE_REQ_RESP,
  > 59				.opcode = GET_CHG_ULOG_REQ
    60			},
    61			.log_size = MAX_ULOG_SIZE
    62		};
    63	
    64		return pmic_pdcharger_ulog_write_async(pg, &req_msg, sizeof(req_msg));
    65	}
    66	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2023-12-05 19:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202312060355.M0eJtq4X-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-mm@kvack.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