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: [vireshk:virtio/msg-xen 7/17] drivers/virtio/virtio_msg_loopback.c:366:1: sparse: sparse: bad integer constant expression
Date: Fri, 16 Jan 2026 16:19:20 +0800	[thread overview]
Message-ID: <202601161638.n9qSegnr-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/virtio/virtio_msg_loopback.c:366:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Viresh Kumar <viresh.kumar@linaro.org>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git virtio/msg-xen
head:   2978a84b82627a16bee8e2cd5718a51de47e7d5e
commit: b7c1464853a66536efb17d2415bdce759a8d7e87 [7/17] virtio-msg: Add loopback bus for testing
:::::: branch date: 23 hours ago
:::::: commit date: 23 hours ago
config: sh-randconfig-r133-20260115 (https://download.01.org/0day-ci/archive/20260116/202601161638.n9qSegnr-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601161638.n9qSegnr-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/202601161638.n9qSegnr-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/virtio/virtio_msg.c:672:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg.c:672:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
   drivers/virtio/virtio_msg.c:673:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg.c:673:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   drivers/virtio/virtio_msg.c:674:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg.c:674:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
--
>> drivers/virtio/virtio_msg_loopback.c:366:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg_loopback.c:366:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
   drivers/virtio/virtio_msg_loopback.c:367:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg_loopback.c:367:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   drivers/virtio/virtio_msg_loopback.c:368:1: sparse: sparse: bad integer constant expression
   drivers/virtio/virtio_msg_loopback.c:368:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"

vim +366 drivers/virtio/virtio_msg_loopback.c

b7c1464853a665 Viresh Kumar 2024-12-10  365  
b7c1464853a665 Viresh Kumar 2024-12-10 @366  MODULE_AUTHOR("Viresh Kumar <viresh.kumar@linaro.org>");

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

                 reply	other threads:[~2026-01-16  8: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=202601161638.n9qSegnr-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.