All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [litex-hub:litex-rebase 3/15] drivers/spi/spi-litespi.c:200:1: sparse: sparse: bad integer constant expression
Date: Sun, 14 Dec 2025 00:37:30 +0800	[thread overview]
Message-ID: <202512140028.IQBNHpu8-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/spi/spi-litespi.c:200:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Filip Kokosinski <fkokosinski@internships.antmicro.com>
CC: Gabriel Somlo <gsomlo@gmail.com>
CC: Geert Uytterhoeven <geert@linux-m68k.org>

tree:   https://github.com/litex-hub/linux litex-rebase
head:   bf1103a7647b9e371007e1f7d02827190e619900
commit: ec2cd6393ed1ce1f080ec2c75b7c835a19e2433e [3/15] LiteX: driver for LiteSPI
:::::: branch date: 5 days ago
:::::: commit date: 5 days ago
config: alpha-randconfig-r112-20251213 (https://download.01.org/0day-ci/archive/20251214/202512140028.IQBNHpu8-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512140028.IQBNHpu8-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/202512140028.IQBNHpu8-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-litespi.c:200:1: sparse: sparse: bad integer constant expression
   drivers/spi/spi-litespi.c:200:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
   drivers/spi/spi-litespi.c:201:1: sparse: sparse: bad integer constant expression
   drivers/spi/spi-litespi.c:201:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
   drivers/spi/spi-litespi.c:202:1: sparse: sparse: bad integer constant expression
   drivers/spi/spi-litespi.c:202:1: sparse: sparse: static assertion failed: "MODULE_INFO(alias, ...) contains embedded NUL byte"

vim +200 drivers/spi/spi-litespi.c

ec2cd6393ed1ce Filip Kokosinski 2020-12-22  199  
ec2cd6393ed1ce Filip Kokosinski 2020-12-22 @200  MODULE_AUTHOR("Antmicro Ltd <www.antmicro.com>");

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

                 reply	other threads:[~2025-12-13 16:38 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=202512140028.IQBNHpu8-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.