From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [gdamjan:v6.19/thinkpad-x9-14 3/6] drivers/media/i2c/imx471.c:993:1: sparse: sparse: bad integer constant expression
Date: Thu, 18 Dec 2025 13:34:52 +0800 [thread overview]
Message-ID: <202512181338.4cd7V1TP-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/media/i2c/imx471.c:993:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Дамјан Георгиевски" <gdamjan@gmail.com>
tree: https://github.com/gdamjan/linux v6.19/thinkpad-x9-14
head: 89f00ee2600546cc930a1fbad7d401bc134d54e4
commit: 59068e36d3e51cc3216628306c6c0a373d8b0d1b [3/6] media: i2c: copy imx471 sensor driver from github.com/intel/ipu6-drivers
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: x86_64-randconfig-122-20251216 (https://download.01.org/0day-ci/archive/20251218/202512181338.4cd7V1TP-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251218/202512181338.4cd7V1TP-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/202512181338.4cd7V1TP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/media/i2c/imx471.c:993:1: sparse: sparse: bad integer constant expression
drivers/media/i2c/imx471.c:993:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/media/i2c/imx471.c:994:1: sparse: sparse: bad integer constant expression
drivers/media/i2c/imx471.c:994:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/media/i2c/imx471.c:995:1: sparse: sparse: bad integer constant expression
drivers/media/i2c/imx471.c:995:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/media/i2c/imx471.c:995:1: sparse: sparse: bad integer constant expression
drivers/media/i2c/imx471.c:995:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +993 drivers/media/i2c/imx471.c
59068e36d3e51c Дамјан Георгиевски 2025-06-26 992
59068e36d3e51c Дамјан Георгиевски 2025-06-26 @993 MODULE_AUTHOR("Jimmy Su <jimmy.su@intel.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-18 5:35 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=202512181338.4cd7V1TP-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.