From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2 2/4] i2c: add Andes I2C driver support
Date: Thu, 22 Jan 2026 23:15:34 +0800 [thread overview]
Message-ID: <202601222235.v6MYfKJs-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/i2c/busses/i2c-andes.c:339:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260122-atciic100-v2-2-7559136d07cf@andestech.com>
References: <20260122-atciic100-v2-2-7559136d07cf@andestech.com>
TO: "Ben Zong-You Xie via B4 Relay" <devnull+ben717.andestech.com@kernel.org>
TO: Andi Shyti <andi.shyti@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Paul Walmsley <pjw@kernel.org>
TO: Palmer Dabbelt <palmer@dabbelt.com>
TO: Albert Ou <aou@eecs.berkeley.edu>
TO: Alexandre Ghiti <alex@ghiti.fr>
CC: linux-i2c@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-riscv@lists.infradead.org
CC: "Ben Zong-You Xie" <ben717@andestech.com>
Hi Ben,
kernel test robot noticed the following build warnings:
[auto build test WARNING on aa5804b8fb64f446260cee45e7e8a722ac7ca839]
url: https://github.com/intel-lab-lkp/linux/commits/Ben-Zong-You-Xie-via-B4-Relay/dt-bindings-i2c-add-support-for-AE350-I2C-controller/20260122-115843
base: aa5804b8fb64f446260cee45e7e8a722ac7ca839
patch link: https://lore.kernel.org/r/20260122-atciic100-v2-2-7559136d07cf%40andestech.com
patch subject: [PATCH v2 2/4] i2c: add Andes I2C driver support
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: mips-randconfig-r133-20260122 (https://download.01.org/0day-ci/archive/20260122/202601222235.v6MYfKJs-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601222235.v6MYfKJs-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/202601222235.v6MYfKJs-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/i2c/busses/i2c-andes.c:339:1: sparse: sparse: bad integer constant expression
drivers/i2c/busses/i2c-andes.c:339:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/i2c/busses/i2c-andes.c:340:1: sparse: sparse: bad integer constant expression
drivers/i2c/busses/i2c-andes.c:340:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/i2c/busses/i2c-andes.c:341:1: sparse: sparse: bad integer constant expression
drivers/i2c/busses/i2c-andes.c:341:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/i2c/busses/i2c-andes.c:341:1: sparse: sparse: bad integer constant expression
drivers/i2c/busses/i2c-andes.c:341:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +339 drivers/i2c/busses/i2c-andes.c
d73a2e5b4946bf Ben Zong-You Xie 2026-01-22 338
d73a2e5b4946bf Ben Zong-You Xie 2026-01-22 @339 MODULE_AUTHOR("Ben Zong-You Xie <ben717@andestech.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-22 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 15:15 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-22 3:53 [PATCH v2 0/4] i2c: add support for Andes platform Ben Zong-You Xie
2026-01-22 3:53 ` [PATCH v2 2/4] i2c: add Andes I2C driver support Ben Zong-You Xie
2026-01-22 3:53 ` Ben Zong-You Xie via B4 Relay
2026-01-22 3:53 ` Ben Zong-You Xie via B4 Relay
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=202601222235.v6MYfKJs-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.