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: Re: [PATCH v8 2/2] phy: eswin: Create eswin directory and add EIC7700 SATA PHY driver
Date: Fri, 23 Jan 2026 21:22:16 +0800	[thread overview]
Message-ID: <202601232108.K5gv4OLc-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/phy/eswin/phy-eic7700-sata.c:271:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260123030933.987-1-luyulin@eswincomputing.com>
References: <20260123030933.987-1-luyulin@eswincomputing.com>
TO: Yulin Lu <luyulin@eswincomputing.com>
TO: vkoul@kernel.org
TO: neil.armstrong@linaro.org
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: p.zabel@pengutronix.de
TO: linux-phy@lists.infradead.org
TO: devicetree@vger.kernel.org
TO: linux-kernel@vger.kernel.org
CC: ningyu@eswincomputing.com
CC: linmin@eswincomputing.com
CC: fenglin@eswincomputing.com
CC: Yulin Lu <luyulin@eswincomputing.com>

Hi Yulin,

kernel test robot noticed the following build warnings:

[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.19-rc6 next-20260122]
[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/Yulin-Lu/dt-bindings-phy-eswin-Document-the-EIC7700-SoC-SATA-PHY/20260123-111201
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:    https://lore.kernel.org/r/20260123030933.987-1-luyulin%40eswincomputing.com
patch subject: [PATCH v8 2/2] phy: eswin: Create eswin directory and add EIC7700 SATA PHY driver
:::::: branch date: 10 hours ago
:::::: commit date: 10 hours ago
config: openrisc-randconfig-r111-20260123 (https://download.01.org/0day-ci/archive/20260123/202601232108.K5gv4OLc-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601232108.K5gv4OLc-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/202601232108.K5gv4OLc-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/phy/eswin/phy-eic7700-sata.c:271:1: sparse: sparse: bad integer constant expression
   drivers/phy/eswin/phy-eic7700-sata.c:271:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   drivers/phy/eswin/phy-eic7700-sata.c:272:1: sparse: sparse: bad integer constant expression
   drivers/phy/eswin/phy-eic7700-sata.c:272:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
   drivers/phy/eswin/phy-eic7700-sata.c:273:1: sparse: sparse: bad integer constant expression
   drivers/phy/eswin/phy-eic7700-sata.c:273:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"

vim +271 drivers/phy/eswin/phy-eic7700-sata.c

1e9a7ab83d6c55 Yulin Lu 2026-01-23  270  
1e9a7ab83d6c55 Yulin Lu 2026-01-23 @271  MODULE_DESCRIPTION("SATA PHY driver for the ESWIN EIC7700 SoC");

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

             reply	other threads:[~2026-01-23 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 13:22 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-23  2:48 [PATCH v8 0/2] Add driver support for Eswin EIC7700 SoC SATA PHY Yulin Lu
2026-01-23  3:09 ` [PATCH v8 2/2] phy: eswin: Create eswin directory and add EIC7700 SATA PHY driver Yulin Lu
2026-01-23  3:09   ` Yulin Lu

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=202601232108.K5gv4OLc-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.