From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] PCI: layerscape: Allow to compile as module
Date: Wed, 14 Jan 2026 01:37:53 +0800 [thread overview]
Message-ID: <202601140109.TZ328ToM-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/pci/controller/dwc/pci-layerscape.c:426:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260112-v6-19-topic-layerscape-pcie-v1-1-1cd863fce50e@pengutronix.de>
References: <20260112-v6-19-topic-layerscape-pcie-v1-1-1cd863fce50e@pengutronix.de>
TO: Steffen Trumtrar <s.trumtrar@pengutronix.de>
TO: Lorenzo Pieralisi <lpieralisi@kernel.org>
TO: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
TO: Manivannan Sadhasivam <mani@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Bjorn Helgaas <helgaas@kernel.org>
TO: Minghuan Lian <minghuan.Lian@nxp.com>
TO: Mingkai Hu <mingkai.hu@nxp.com>
TO: Roy Zang <roy.zang@nxp.com>
TO: Jingoo Han <jingoohan1@gmail.com>
CC: linux-pci@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linuxppc-dev@lists.ozlabs.org
CC: linux-arm-kernel@lists.infradead.org
CC: imx@lists.linux.dev
CC: Sascha Hauer <s.hauer@pengutronix.de>
CC: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Hi Steffen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8f0b4cce4481fb22653697cced8d0d04027cb1e8]
url: https://github.com/intel-lab-lkp/linux/commits/Steffen-Trumtrar/PCI-layerscape-Allow-to-compile-as-module/20260113-031840
base: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
patch link: https://lore.kernel.org/r/20260112-v6-19-topic-layerscape-pcie-v1-1-1cd863fce50e%40pengutronix.de
patch subject: [PATCH] PCI: layerscape: Allow to compile as module
:::::: branch date: 22 hours ago
:::::: commit date: 22 hours ago
config: arm64-randconfig-r121-20260113 (https://download.01.org/0day-ci/archive/20260114/202601140109.TZ328ToM-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260114/202601140109.TZ328ToM-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/202601140109.TZ328ToM-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/controller/dwc/pci-layerscape.c:426:1: sparse: sparse: bad integer constant expression
drivers/pci/controller/dwc/pci-layerscape.c:426:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
drivers/pci/controller/dwc/pci-layerscape.c:427:1: sparse: sparse: bad integer constant expression
drivers/pci/controller/dwc/pci-layerscape.c:427:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/pci/controller/dwc/pci-layerscape.c:428:1: sparse: sparse: bad integer constant expression
drivers/pci/controller/dwc/pci-layerscape.c:428:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/pci/controller/dwc/pci-layerscape.c:428:1: sparse: sparse: bad integer constant expression
drivers/pci/controller/dwc/pci-layerscape.c:428:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +426 drivers/pci/controller/dwc/pci-layerscape.c
dec661c9cf9ebf Sascha Hauer 2026-01-12 425
dec661c9cf9ebf Sascha Hauer 2026-01-12 @426 MODULE_AUTHOR("Minghuan Lian <Minghuan.Lian@freescale.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-13 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:37 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 19:17 [PATCH] PCI: layerscape: Allow to compile as module Steffen Trumtrar
2026-01-12 20:20 ` Roy Zang
2026-02-16 21:49 ` Marc Kleine-Budde
2026-02-17 14:00 ` Manivannan Sadhasivam
2026-02-26 6:33 ` Manivannan Sadhasivam
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=202601140109.TZ328ToM-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.