0 day kernel build service
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 2/3] watchdog: atcwdt200: Add driver for Andes ATCWDT200
Date: Sun, 11 Jan 2026 06:19:00 +0800	[thread overview]
Message-ID: <202601110510.7ItbCM9e-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/watchdog/atcwdt200_wdt.c:586:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260107145058.213334-3-cl634@andestech.com>
References: <20260107145058.213334-3-cl634@andestech.com>
TO: CL Wang <cl634@andestech.com>
TO: cl634@andestech.com
TO: wim@linux-watchdog.org
TO: linux@roeck-us.net
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-watchdog@vger.kernel.org
CC: tim609@andestech.com

Hi CL,

kernel test robot noticed the following build warnings:

[auto build test WARNING on robh/for-next]
[also build test WARNING on groeck-staging/hwmon-next linus/master v6.19-rc4 next-20260109]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/CL-Wang/dt-bindings-watchdog-Add-support-for-Andes-ATCWDT200/20260107-233010
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:    https://lore.kernel.org/r/20260107145058.213334-3-cl634%40andestech.com
patch subject: [PATCH 2/3] watchdog: atcwdt200: Add driver for Andes ATCWDT200
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: arm64-randconfig-r112-20260110 (https://download.01.org/0day-ci/archive/20260111/202601110510.7ItbCM9e-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260111/202601110510.7ItbCM9e-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/202601110510.7ItbCM9e-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/watchdog/atcwdt200_wdt.c:586:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:586:1: sparse: sparse: static assertion failed: "MODULE_INFO(parmtype, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:587:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:587:1: sparse: sparse: static assertion failed: "MODULE_INFO(parm, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:590:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:590:1: sparse: sparse: static assertion failed: "MODULE_INFO(parmtype, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:591:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:591:1: sparse: sparse: static assertion failed: "MODULE_INFO(parm, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:594:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:594:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:595:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:595:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
   drivers/watchdog/atcwdt200_wdt.c:596:1: sparse: sparse: bad integer constant expression
   drivers/watchdog/atcwdt200_wdt.c:596:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"

vim +586 drivers/watchdog/atcwdt200_wdt.c

22003ac2445ca8c CL Wang 2026-01-07  585  
22003ac2445ca8c CL Wang 2026-01-07 @586  module_param(timeout, uint, 0);
22003ac2445ca8c CL Wang 2026-01-07  587  MODULE_PARM_DESC(timeout, "Watchdog timeout in seconds (default="
22003ac2445ca8c CL Wang 2026-01-07  588  		 __MODULE_STRING(ATCWDT_TIMEOUT) ")");
22003ac2445ca8c CL Wang 2026-01-07  589  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-01-10 22: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=202601110510.7ItbCM9e-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