From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jic23-iio:testing 14/66] drivers/iio/adc/ti-ads131m02.c:966:1: sparse: sparse: bad integer constant expression
Date: Fri, 02 Jan 2026 02:12:16 +0800 [thread overview]
Message-ID: <202601020246.OSSCR7Pb-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/iio/adc/ti-ads131m02.c:966:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: David Jander <david@protonic.nl>
CC: Jonathan Cameron <Jonathan.Cameron@huawei.com>
CC: Oleksij Rempel <o.rempel@pengutronix.de>
CC: David Lechner <dlechner@baylibre.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
head: fb2f4eb29a258145b0336601f00509cab6e93e7c
commit: 4aa91223fd6c9b9e6c73f9dc6ffb55cbf04df4ac [14/66] iio: adc: Add TI ADS131M0x ADC driver
:::::: branch date: 25 hours ago
:::::: commit date: 11 days ago
config: openrisc-randconfig-r133-20260101 (https://download.01.org/0day-ci/archive/20260102/202601020246.OSSCR7Pb-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260102/202601020246.OSSCR7Pb-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/202601020246.OSSCR7Pb-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/adc/ti-ads131m02.c:966:1: sparse: sparse: bad integer constant expression
drivers/iio/adc/ti-ads131m02.c:966:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/iio/adc/ti-ads131m02.c:967:1: sparse: sparse: bad integer constant expression
drivers/iio/adc/ti-ads131m02.c:967:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/iio/adc/ti-ads131m02.c:968:1: sparse: sparse: bad integer constant expression
drivers/iio/adc/ti-ads131m02.c:968:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +966 drivers/iio/adc/ti-ads131m02.c
4aa91223fd6c9b David Jander 2025-11-18 965
4aa91223fd6c9b David Jander 2025-11-18 @966 MODULE_AUTHOR("David Jander <david@protonic.nl>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-01 18:12 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=202601020246.OSSCR7Pb-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.