From: kernel test robot <lkp@intel.com>
To: Thierry Reding <thierry.reding@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Karthikeyan Mitran" <m.karthikeyan@mobiveil.co.in>,
"Hou Zhiqiang" <Zhiqiang.Hou@nxp.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Pali Rohár" <pali@kernel.org>, "Michal Simek" <monstr@monstr.eu>,
"Kevin Xie" <kevin.xie@starfivetech.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Use standard wait times for PCIe link monitoring
Date: Sat, 21 Mar 2026 17:44:59 +0800 [thread overview]
Message-ID: <202603211715.0eQRORig-lkp@intel.com> (raw)
In-Reply-To: <20260320224044.2569907-1-thierry.reding@kernel.org>
Hi Thierry,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v7.0-rc4 next-20260320]
[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/Thierry-Reding/PCI-Use-standard-wait-times-for-PCIe-link-monitoring/20260321-100847
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20260320224044.2569907-1-thierry.reding%40kernel.org
patch subject: [PATCH] PCI: Use standard wait times for PCIe link monitoring
config: s390-randconfig-001-20260321 (https://download.01.org/0day-ci/archive/20260321/202603211715.0eQRORig-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260321/202603211715.0eQRORig-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/oe-kbuild-all/202603211715.0eQRORig-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/pci/controller/cadence/pcie-cadence-host-common.c: In function 'cdns_pcie_host_wait_for_link':
>> drivers/pci/controller/cadence/pcie-cadence-host-common.c:56:37: error: 'PCIE_LINK_WAIT_MAX_RETRIES' undeclared (first use in this function)
56 | for (retries = 0; retries < PCIE_LINK_WAIT_MAX_RETRIES; retries++) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/pci/controller/cadence/pcie-cadence-host-common.c:56:37: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/pci/controller/cadence/pcie-cadence-host-common.c:61:30: error: 'PCIE_LINK_WAIT_US_MIN' undeclared (first use in this function)
61 | usleep_range(PCIE_LINK_WAIT_US_MIN, PCIE_LINK_WAIT_US_MAX);
| ^~~~~~~~~~~~~~~~~~~~~
>> drivers/pci/controller/cadence/pcie-cadence-host-common.c:61:53: error: 'PCIE_LINK_WAIT_US_MAX' undeclared (first use in this function)
61 | usleep_range(PCIE_LINK_WAIT_US_MIN, PCIE_LINK_WAIT_US_MAX);
| ^~~~~~~~~~~~~~~~~~~~~
vim +/PCIE_LINK_WAIT_MAX_RETRIES +56 drivers/pci/controller/cadence/pcie-cadence-host-common.c
48
49 int cdns_pcie_host_wait_for_link(struct cdns_pcie *pcie,
50 cdns_pcie_linkup_func pcie_link_up)
51 {
52 struct device *dev = pcie->dev;
53 int retries;
54
55 /* Check if the link is up or not */
> 56 for (retries = 0; retries < PCIE_LINK_WAIT_MAX_RETRIES; retries++) {
57 if (pcie_link_up(pcie)) {
58 dev_info(dev, "Link up\n");
59 return 0;
60 }
> 61 usleep_range(PCIE_LINK_WAIT_US_MIN, PCIE_LINK_WAIT_US_MAX);
62 }
63
64 return -ETIMEDOUT;
65 }
66 EXPORT_SYMBOL_GPL(cdns_pcie_host_wait_for_link);
67
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-21 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 22:40 [PATCH] PCI: Use standard wait times for PCIe link monitoring Thierry Reding
2026-03-20 22:47 ` Thierry Reding
2026-03-21 9:44 ` kernel test robot [this message]
2026-03-21 10:17 ` kernel test robot
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=202603211715.0eQRORig-lkp@intel.com \
--to=lkp@intel.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=helgaas@kernel.org \
--cc=kevin.xie@starfivetech.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=m.karthikeyan@mobiveil.co.in \
--cc=mani@kernel.org \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox