From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jgunthorpe:iommu_pt_riscv 6/7] drivers/iommu/riscv/iommu.c:1468:1: sparse: sparse: bad integer constant expression
Date: Wed, 24 Dec 2025 12:30:17 +0800 [thread overview]
Message-ID: <202512241220.omy7JfKd-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/iommu/riscv/iommu.c:1468:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jason Gunthorpe <jgg@nvidia.com>
tree: https://github.com/jgunthorpe/linux iommu_pt_riscv
head: cde8a040db2d66ed49a2e93a0bbbbbf1cb83d7a7
commit: 937e886354f0940f3d8506553007cea935b81646 [6/7] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST
:::::: branch date: 5 days ago
:::::: commit date: 5 days ago
config: loongarch-randconfig-r121-20251224 (https://download.01.org/0day-ci/archive/20251224/202512241220.omy7JfKd-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512241220.omy7JfKd-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/r/202512241220.omy7JfKd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
drivers/iommu/riscv/iommu.c:1380:13: sparse: sparse: too long token expansion
>> drivers/iommu/riscv/iommu.c:1468:1: sparse: sparse: bad integer constant expression
drivers/iommu/riscv/iommu.c:1468:1: sparse: sparse: static assertion failed: "MODULE_INFO(import_ns, ...) contains embedded NUL byte"
vim +1468 drivers/iommu/riscv/iommu.c
e89e825351115d Jason Gunthorpe 2025-05-07 1467
e89e825351115d Jason Gunthorpe 2025-05-07 @1468 MODULE_IMPORT_NS("GENERIC_PT_IOMMU");
:::::: The code at line 1468 was first introduced by commit
:::::: e89e825351115d0aaec359d3651f28c4913a476f iommu/riscv: Use the generic iommu page table
:::::: TO: Jason Gunthorpe <jgg@nvidia.com>
:::::: CC: Jason Gunthorpe <jgg@nvidia.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-24 4:31 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=202512241220.omy7JfKd-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.