From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 1/1] drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:4669:25: sparse: sparse: incorrect type in argument 4 (different base types)
Date: Fri, 16 Oct 2026 18:35:41 +0200 [thread overview]
Message-ID: <202610161859.oKWHrBeh-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6
head: b9d5e9a3a59c79fd6ec703c9780ab38ad1c0505d
commit: 8be15087d03752ee6b53e54bd962f0ecf9bb5658 [1/1] scsi: hisi_sas: Use macro instead of magic number
config: arm64-randconfig-r2307-20261016 (https://download.01.org/0day-ci/archive/20261016/202610161859.oKWHrBeh-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 8a679464f19c426ef76aad9f4587b703dd3e584d)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261016/202610161859.oKWHrBeh-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/202610161859.oKWHrBeh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:1492:26: sparse: sparse: invalid assignment: |=
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:1492:26: sparse: left side has type restricted __le32
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:1492:26: sparse: right side has type unsigned int
>> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:4669:25: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted __le32 [usertype] *[assigned] ptr @@ got unsigned int * @@
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:4669:25: sparse: expected restricted __le32 [usertype] *[assigned] ptr
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:4669:25: sparse: got unsigned int *
vim +4669 drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
4660
4661 static int debugfs_fifo_data_v3_hw_show(struct seq_file *s, void *p)
4662 {
4663 struct hisi_sas_phy *phy = s->private;
4664
4665 debugfs_read_fifo_data_v3_hw(phy);
4666
4667 debugfs_show_row_32_v3_hw(s, 0,
4668 HISI_SAS_FIFO_DATA_DW_SIZE * HISI_SAS_REG_MEM_SIZE,
> 4669 phy->fifo.rd_data);
4670
4671 return 0;
4672 }
4673 DEFINE_SHOW_ATTRIBUTE(debugfs_fifo_data_v3_hw);
4674
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-16 16:36 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=202610161859.oKWHrBeh-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 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.