From: kernel test robot <lkp@intel.com>
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Subject: Re: [PATCH] PCI: qcom: Add register dump support for PCIe Link Down events
Date: Thu, 20 Aug 2026 13:09:44 +0800 [thread overview]
Message-ID: <202608201351.dBcT51sv-lkp@intel.com> (raw)
In-Reply-To: <20260811-regdump-v1-1-f22db3fb37c2@oss.qualcomm.com>
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d55d5a8f3d852baab49dba910dcb04b6d8091b05]
url: https://github.com/intel-lab-lkp/linux/commits/Krishna-Chaitanya-Chundru/PCI-qcom-Add-register-dump-support-for-PCIe-Link-Down-events/20260811-214223
base: d55d5a8f3d852baab49dba910dcb04b6d8091b05
patch link: https://lore.kernel.org/r/20260811-regdump-v1-1-f22db3fb37c2%40oss.qualcomm.com
patch subject: [PATCH] PCI: qcom: Add register dump support for PCIe Link Down events
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20260820/202608201351.dBcT51sv-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260820/202608201351.dBcT51sv-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/202608201351.dBcT51sv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/pci/controller/dwc/pcie-qcom.c:220:18: warning: 'qcom_pcie_ext_parf_dump_regs' defined but not used [-Wunused-const-variable=]
220 | static const u32 qcom_pcie_ext_parf_dump_regs[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/qcom_pcie_ext_parf_dump_regs +220 drivers/pci/controller/dwc/pcie-qcom.c
219
> 220 static const u32 qcom_pcie_ext_parf_dump_regs[] = {
221 PARF_PM_STTS,
222 PARF_PM_STTS_1,
223 PARF_INT_ALL_STATUS,
224 PARF_INT_ALL_2_STATUS,
225 PARF_CLKREQ_OVERRIDE,
226 PARF_L1SS_SLEEP_MODE_HANDLER_STATUS,
227 PARF_L1SS_SLEEP_MODE_HANDLER_CFG,
228 PARF_CORE_ERRORS,
229 PARF_LINK_DOWN_AXI_ECAM_BLOCK_STATUS,
230 PARF_STATUS,
231 PARF_SYS_CTRL,
232 };
233
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-20 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 16:12 [PATCH] PCI: qcom: Add register dump support for PCIe Link Down events Krishna Chaitanya Chundru
2026-08-19 10:45 ` Konrad Dybcio
2026-08-20 5:09 ` kernel test robot [this message]
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=202608201351.dBcT51sv-lkp@intel.com \
--to=lkp@intel.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
/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