From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 5562/6771] drivers/interconnect/icc-kunit.c:322:1: sparse: sparse: bad integer constant expression
Date: Thu, 15 Jan 2026 22:21:59 +0800 [thread overview]
Message-ID: <202601152219.wp7TKZXT-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/interconnect/icc-kunit.c:322:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Kuan-Wei Chiu" <visitorckw@gmail.com>
CC: Georgi Djakov <djakov@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 9b7977f9e39b7768c70c2aa497f04e7569fd3e00
commit: 06ebbe719bb022795cd9def0606a6805b1f2f755 [5562/6771] interconnect: Add kunit tests for core functionality
:::::: branch date: 9 hours ago
:::::: commit date: 2 days ago
config: microblaze-randconfig-r132-20260115 (https://download.01.org/0day-ci/archive/20260115/202601152219.wp7TKZXT-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260115/202601152219.wp7TKZXT-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/202601152219.wp7TKZXT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/interconnect/icc-kunit.c:322:1: sparse: sparse: bad integer constant expression
drivers/interconnect/icc-kunit.c:322:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/interconnect/icc-kunit.c:323:1: sparse: sparse: bad integer constant expression
drivers/interconnect/icc-kunit.c:323:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/interconnect/icc-kunit.c:324:1: sparse: sparse: bad integer constant expression
drivers/interconnect/icc-kunit.c:324:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/interconnect/icc-kunit.c:324:1: sparse: sparse: bad integer constant expression
drivers/interconnect/icc-kunit.c:324:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +322 drivers/interconnect/icc-kunit.c
06ebbe719bb022 Kuan-Wei Chiu 2026-01-10 321
06ebbe719bb022 Kuan-Wei Chiu 2026-01-10 @322 MODULE_AUTHOR("Kuan-Wei Chiu <visitorckw@gmail.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-15 14:22 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=202601152219.wp7TKZXT-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.