From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v7 2/4] backlight: add max25014atg backlight
Date: Sat, 24 Jan 2026 09:42:57 +0800 [thread overview]
Message-ID: <202601240933.cKsG1DN2-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/video/backlight/max25014.c:375:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260123-max25014-v7-2-15e504b9acc7@gocontroll.com>
References: <20260123-max25014-v7-2-15e504b9acc7@gocontroll.com>
TO: Maud Spierings via B4 Relay <devnull+maudspierings.gocontroll.com@kernel.org>
TO: Lee Jones <lee@kernel.org>
TO: Daniel Thompson <danielt@kernel.org>
TO: Jingoo Han <jingoohan1@gmail.com>
TO: Pavel Machek <pavel@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Helge Deller <deller@gmx.de>
TO: Shawn Guo <shawnguo@kernel.org>
TO: Sascha Hauer <s.hauer@pengutronix.de>
TO: Pengutronix Kernel Team <kernel@pengutronix.de>
TO: Fabio Estevam <festevam@gmail.com>
TO: Liam Girdwood <lgirdwood@gmail.com>
TO: Mark Brown <broonie@kernel.org>
CC: dri-devel@lists.freedesktop.org
CC: linux-leds@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-fbdev@vger.kernel.org
CC: imx@lists.linux.dev
CC: linux-arm-kernel@lists.infradead.org
CC: Maud Spierings <maudspierings@gocontroll.com>
Hi Maud,
kernel test robot noticed the following build warnings:
[auto build test WARNING on a0c666c25aeefd16f4b088c6549a6fb6b65a8a1d]
url: https://github.com/intel-lab-lkp/linux/commits/Maud-Spierings-via-B4-Relay/dt-bindings-backlight-Add-max25014-support/20260123-193429
base: a0c666c25aeefd16f4b088c6549a6fb6b65a8a1d
patch link: https://lore.kernel.org/r/20260123-max25014-v7-2-15e504b9acc7%40gocontroll.com
patch subject: [PATCH v7 2/4] backlight: add max25014atg backlight
:::::: branch date: 14 hours ago
:::::: commit date: 14 hours ago
config: nios2-randconfig-r113-20260124 (https://download.01.org/0day-ci/archive/20260124/202601240933.cKsG1DN2-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260124/202601240933.cKsG1DN2-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/202601240933.cKsG1DN2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/video/backlight/max25014.c:375:1: sparse: sparse: bad integer constant expression
drivers/video/backlight/max25014.c:375:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/video/backlight/max25014.c:376:1: sparse: sparse: bad integer constant expression
drivers/video/backlight/max25014.c:376:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/video/backlight/max25014.c:377:1: sparse: sparse: bad integer constant expression
drivers/video/backlight/max25014.c:377:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +375 drivers/video/backlight/max25014.c
7d129add59bae00 Maud Spierings 2026-01-23 374
7d129add59bae00 Maud Spierings 2026-01-23 @375 MODULE_DESCRIPTION("Maxim MAX25014 backlight driver");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-24 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 1:42 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-23 11:31 [PATCH v7 0/4] backlight: add new max25014 backlight driver Maud Spierings
2026-01-23 11:31 ` [PATCH v7 2/4] backlight: add max25014atg backlight Maud Spierings
2026-01-23 11:31 ` Maud Spierings via B4 Relay
2026-03-04 10:38 ` Daniel Thompson
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=202601240933.cKsG1DN2-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.