From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 1815/5095] drivers/hwmon/pmbus/mp5926.c:181:1: sparse: sparse: bad integer constant expression
Date: Mon, 12 Jan 2026 03:19:02 +0800 [thread overview]
Message-ID: <202601120341.amlGG4BK-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/hwmon/pmbus/mp5926.c:181:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Yuxi Wang <Yuxi.Wang@monolithicpower.com>
CC: Guenter Roeck <linux@roeck-us.net>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f417b7ffcbef7d76b0d8860518f50dae0e7e5eda
commit: c6c80820ac5d845c19c4de2e6054e7c246017044 [1815/5095] hwmon: (pmbus) Add mp5926 driver
:::::: branch date: 3 days ago
:::::: commit date: 3 weeks ago
config: openrisc-randconfig-r122-20260111 (https://download.01.org/0day-ci/archive/20260112/202601120341.amlGG4BK-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260112/202601120341.amlGG4BK-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/202601120341.amlGG4BK-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/hwmon/pmbus/mp5926.c:181:1: sparse: sparse: bad integer constant expression
drivers/hwmon/pmbus/mp5926.c:181:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/hwmon/pmbus/mp5926.c:182:1: sparse: sparse: bad integer constant expression
drivers/hwmon/pmbus/mp5926.c:182:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/hwmon/pmbus/mp5926.c:183:1: sparse: sparse: bad integer constant expression
drivers/hwmon/pmbus/mp5926.c:183:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/hwmon/pmbus/mp5926.c:183:1: sparse: sparse: bad integer constant expression
drivers/hwmon/pmbus/mp5926.c:183:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
drivers/hwmon/pmbus/mp5926.c:184:1: sparse: sparse: bad integer constant expression
drivers/hwmon/pmbus/mp5926.c:184:1: sparse: sparse: static assertion failed: "MODULE_INFO(import_ns, ...) contains embedded NUL byte"
vim +181 drivers/hwmon/pmbus/mp5926.c
c6c80820ac5d84 Yuxi Wang 2025-12-19 179
c6c80820ac5d84 Yuxi Wang 2025-12-19 180 module_i2c_driver(mp5926_driver);
c6c80820ac5d84 Yuxi Wang 2025-12-19 @181 MODULE_AUTHOR("Yuxi Wang <Yuxi.Wang@monolithicpower.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-11 19:19 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=202601120341.amlGG4BK-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox