From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 1/8] Add Advantech EIO MFD driver
Date: Sun, 14 Dec 2025 07:12:25 +0800 [thread overview]
Message-ID: <202512140653.VFtpkQVM-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/mfd/eio_core.c:39:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251212-upstream-v1-v1-1-d50d40ec8d8a@advantech.com>
References: <20251212-upstream-v1-v1-1-d50d40ec8d8a@advantech.com>
TO: Ramiro Oliveira <ramiro.oliveira@advantech.com>
TO: Lee Jones <lee@kernel.org>
TO: Linus Walleij <linusw@kernel.org>
TO: Bartosz Golaszewski <brgl@kernel.org>
TO: Guenter Roeck <linux@roeck-us.net>
TO: Andi Shyti <andi.shyti@kernel.org>
TO: Daniel Thompson <danielt@kernel.org>
TO: Jingoo Han <jingoohan1@gmail.com>
TO: Helge Deller <deller@gmx.de>
TO: Wim Van Sebroeck <wim@linux-watchdog.org>
TO: "Rafael J. Wysocki" <rafael@kernel.org>
TO: Daniel Lezcano <daniel.lezcano@linaro.org>
TO: Zhang Rui <rui.zhang@intel.com>
TO: Lukasz Luba <lukasz.luba@arm.com>
CC: linux-kernel@vger.kernel.org
CC: linux-gpio@vger.kernel.org
CC: linux-hwmon@vger.kernel.org
CC: linux-i2c@vger.kernel.org
CC: dri-devel@lists.freedesktop.org
CC: linux-fbdev@vger.kernel.org
CC: linux-watchdog@vger.kernel.org
CC: linux-pm@vger.kernel.org
CC: Wenkai Chung <wenkai.chung@advantech.com.tw>
CC: "Francisco Aragon-Trivino" <francisco.aragon-trivino@advantech.com>
CC: Hongzhi Wang <hongzhi.wang@advantech.com>
CC: Mikhail Tsukerman <mikhail.tsukerman@advantech.com>
CC: Thomas Kastner <thomas.kastner@advantech.com>
CC: Ramiro Oliveira <ramiro.oliveira@advantech.com>
Hi Ramiro,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d9771d0dbe18dd643760431870a6abf9b0866bb0]
url: https://github.com/intel-lab-lkp/linux/commits/Ramiro-Oliveira/Add-Advantech-EIO-MFD-driver/20251213-004905
base: d9771d0dbe18dd643760431870a6abf9b0866bb0
patch link: https://lore.kernel.org/r/20251212-upstream-v1-v1-1-d50d40ec8d8a%40advantech.com
patch subject: [PATCH 1/8] Add Advantech EIO MFD driver
:::::: branch date: 30 hours ago
:::::: commit date: 30 hours ago
config: powerpc-randconfig-r123-20251213 (https://download.01.org/0day-ci/archive/20251214/202512140653.VFtpkQVM-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512140653.VFtpkQVM-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/202512140653.VFtpkQVM-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mfd/eio_core.c:39:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:39:1: sparse: sparse: static assertion failed: "MODULE_INFO(parmtype, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:40:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:40:1: sparse: sparse: static assertion failed: "MODULE_INFO(parm, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:618:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:618:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:619:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:619:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:620:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:620:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:621:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:621:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/mfd/eio_core.c:621:1: sparse: sparse: bad integer constant expression
drivers/mfd/eio_core.c:621:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +39 drivers/mfd/eio_core.c
3265ff741af01a Ramiro Oliveira 2025-12-12 29
3265ff741af01a Ramiro Oliveira 2025-12-12 30 /**
3265ff741af01a Ramiro Oliveira 2025-12-12 31 * Timeout: Default timeout in microseconds when a PMC command's
3265ff741af01a Ramiro Oliveira 2025-12-12 32 * timeout is unspecified. PMC command responses typically range
3265ff741af01a Ramiro Oliveira 2025-12-12 33 * from 200us to 2ms. 5ms is quite a safe value for timeout. In
3265ff741af01a Ramiro Oliveira 2025-12-12 34 * In some cases, responses are longer. In such situations, please
3265ff741af01a Ramiro Oliveira 2025-12-12 35 * adding the timeout parameter loading related sub-drivers or
3265ff741af01a Ramiro Oliveira 2025-12-12 36 * this core driver (not recommended).
3265ff741af01a Ramiro Oliveira 2025-12-12 37 */
3265ff741af01a Ramiro Oliveira 2025-12-12 38 static uint timeout = DEFAULT_TIMEOUT;
3265ff741af01a Ramiro Oliveira 2025-12-12 @39 module_param(timeout, uint, 0444);
3265ff741af01a Ramiro Oliveira 2025-12-12 40 MODULE_PARM_DESC(timeout, "Default PMC command timeout in usec.\n");
3265ff741af01a Ramiro Oliveira 2025-12-12 41
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-13 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 23:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-12 16:40 [PATCH 0/8] Add support for Advantech EIO MFD series devices Ramiro Oliveira
2025-12-12 16:40 ` [PATCH 1/8] Add Advantech EIO MFD driver Ramiro Oliveira
2025-12-13 15:19 ` kernel test robot
2026-01-08 14:45 ` Lee Jones
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=202512140653.VFtpkQVM-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.