From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 13543/13567] drivers/ufs/host/ufs-amd-versal2.c:562:1: sparse: sparse: bad integer constant expression
Date: Mon, 8 Dec 2025 18:54:33 +0800 [thread overview]
Message-ID: <202512081802.UrdFdJdY-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/ufs/host/ufs-amd-versal2.c:562:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: James Bottomley <James.Bottomley@HansenPartnership.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 82bcd04d124a4d84580ea4a8ba6b120db5f512e7
commit: 7fb99b824cc8b3a4b521f7935256d90e7ab14687 [13543/13567] Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git
:::::: branch date: 9 hours ago
:::::: commit date: 3 days ago
config: arc-randconfig-r132-20251208 (https://download.01.org/0day-ci/archive/20251208/202512081802.UrdFdJdY-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251208/202512081802.UrdFdJdY-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/202512081802.UrdFdJdY-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/ufs/host/ufs-amd-versal2.c:562:1: sparse: sparse: bad integer constant expression
>> drivers/ufs/host/ufs-amd-versal2.c:562:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/ufs/host/ufs-amd-versal2.c:563:1: sparse: sparse: bad integer constant expression
>> drivers/ufs/host/ufs-amd-versal2.c:563:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/ufs/host/ufs-amd-versal2.c:564:1: sparse: sparse: bad integer constant expression
>> drivers/ufs/host/ufs-amd-versal2.c:564:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/ufs/host/ufs-amd-versal2.c:564:1: sparse: sparse: bad integer constant expression
>> drivers/ufs/host/ufs-amd-versal2.c:564:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +562 drivers/ufs/host/ufs-amd-versal2.c
769b8b2ffded4c Sai Krishna Potthuri 2025-10-21 561
769b8b2ffded4c Sai Krishna Potthuri 2025-10-21 @562 MODULE_AUTHOR("Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>");
769b8b2ffded4c Sai Krishna Potthuri 2025-10-21 @563 MODULE_DESCRIPTION("AMD Versal Gen 2 UFS Host Controller driver");
769b8b2ffded4c Sai Krishna Potthuri 2025-10-21 @564 MODULE_LICENSE("GPL");
:::::: The code at line 562 was first introduced by commit
:::::: 769b8b2ffded4cd880669edd83e2952efeeb27f7 scsi: ufs: amd-versal2: Add UFS support for AMD Versal Gen 2 SoC
:::::: TO: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
:::::: CC: Martin K. Petersen <martin.petersen@oracle.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-08 10:54 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=202512081802.UrdFdJdY-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.