From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v10 3/7] iommu: Add verisilicon IOMMU driver
Date: Wed, 17 Dec 2025 17:58:12 +0800 [thread overview]
Message-ID: <202512171744.CoKV8Dri-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/iommu/vsi-iommu.c:806:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251215085349.10155-4-benjamin.gaignard@collabora.com>
References: <20251215085349.10155-4-benjamin.gaignard@collabora.com>
TO: Benjamin Gaignard <benjamin.gaignard@collabora.com>
TO: joro@8bytes.org
TO: will@kernel.org
TO: robin.murphy@arm.com
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: heiko@sntech.de
TO: nicolas.dufresne@collabora.com
TO: p.zabel@pengutronix.de
TO: mchehab@kernel.org
CC: iommu@lists.linux.dev
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-rockchip@lists.infradead.org
CC: linux-media@vger.kernel.org
CC: kernel@collabora.com
CC: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Hi Benjamin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.19-rc1 next-20251217]
[cannot apply to robh/for-next rockchip/for-next arm64/for-next/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Benjamin-Gaignard/dt-bindings-vendor-prefixes-Add-Verisilicon/20251215-165740
base: linus/master
patch link: https://lore.kernel.org/r/20251215085349.10155-4-benjamin.gaignard%40collabora.com
patch subject: [PATCH v10 3/7] iommu: Add verisilicon IOMMU driver
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: parisc-randconfig-r123-20251216 (https://download.01.org/0day-ci/archive/20251217/202512171744.CoKV8Dri-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251217/202512171744.CoKV8Dri-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/202512171744.CoKV8Dri-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/vsi-iommu.c:806:1: sparse: sparse: bad integer constant expression
drivers/iommu/vsi-iommu.c:806:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
>> drivers/iommu/vsi-iommu.c:806:1: sparse: sparse: bad integer constant expression
drivers/iommu/vsi-iommu.c:806:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
drivers/iommu/vsi-iommu.c:807:1: sparse: sparse: bad integer constant expression
drivers/iommu/vsi-iommu.c:807:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/iommu/vsi-iommu.c:808:1: sparse: sparse: bad integer constant expression
drivers/iommu/vsi-iommu.c:808:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
vim +806 drivers/iommu/vsi-iommu.c
b9e3cd4bea55cd Benjamin Gaignard 2025-12-15 805
b9e3cd4bea55cd Benjamin Gaignard 2025-12-15 @806 MODULE_LICENSE("GPL");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-17 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 9:58 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-15 8:53 [PATCH v10 0/7] Add support for Verisilicon IOMMU used by media Benjamin Gaignard
2025-12-15 8:53 ` [PATCH v10 3/7] iommu: Add verisilicon IOMMU driver Benjamin Gaignard
2025-12-15 8:53 ` Benjamin Gaignard
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=202512171744.CoKV8Dri-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.