From: kernel test robot <lkp@intel.com>
To: Hans Zhang <18255117159@163.com>,
lpieralisi@kernel.org, bhelgaas@google.com, mani@kernel.org,
kwilczynski@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, robh@kernel.org,
jingoohan1@gmail.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans Zhang <18255117159@163.com>
Subject: Re: [PATCH v3] PCI: dwc: Refactor code by using dw_pcie_clear_and_set_dword()
Date: Sat, 28 Jun 2025 06:20:12 +0800 [thread overview]
Message-ID: <202506280542.6ttkdrur-lkp@intel.com> (raw)
In-Reply-To: <20250626145040.14180-3-18255117159@163.com>
Hi Hans,
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 v6.16-rc3 next-20250627]
[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/Hans-Zhang/PCI-dwc-Refactor-code-by-using-dw_pcie_clear_and_set_dword/20250627-031223
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20250626145040.14180-3-18255117159%40163.com
patch subject: [PATCH v3] PCI: dwc: Refactor code by using dw_pcie_clear_and_set_dword()
config: arc-randconfig-001-20250628 (https://download.01.org/0day-ci/archive/20250628/202506280542.6ttkdrur-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250628/202506280542.6ttkdrur-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/202506280542.6ttkdrur-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/pci/controller/dwc/pcie-amd-mdb.c:21:
drivers/pci/controller/dwc/pcie-designware.h: In function 'dw_pcie_dbi_ro_wr_en':
>> drivers/pci/controller/dwc/pcie-designware.h:712:2: error: implicit declaration of function 'dw_pcie_clear_and_set_dword'; did you mean 'pcie_capability_set_dword'? [-Werror=implicit-function-declaration]
dw_pcie_clear_and_set_dword(pci, PCIE_MISC_CONTROL_1_OFF,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
pcie_capability_set_dword
cc1: some warnings being treated as errors
vim +712 drivers/pci/controller/dwc/pcie-designware.h
709
710 static inline void dw_pcie_dbi_ro_wr_en(struct dw_pcie *pci)
711 {
> 712 dw_pcie_clear_and_set_dword(pci, PCIE_MISC_CONTROL_1_OFF,
713 0, PCIE_DBI_RO_WR_EN);
714 }
715
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-27 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:50 [PATCH v3 00/13] PCI: dwc: Refactor register access with dw_pcie_clear_and_set_dword helper Hans Zhang
2025-06-26 14:50 ` [PATCH v3 01/13] PCI: dwc: Add dw_pcie_clear_and_set_dword() for register bit manipulation Hans Zhang
2025-06-26 14:50 ` [PATCH v3] PCI: dwc: Refactor code by using dw_pcie_clear_and_set_dword() Hans Zhang
2025-06-26 14:55 ` Hans Zhang
2025-06-27 22:20 ` kernel test robot [this message]
2025-06-28 15:44 ` Hans Zhang
2025-06-26 14:50 ` [PATCH v3 03/13] PCI: dra7xx: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 04/13] PCI: imx6: " Hans Zhang
2025-06-26 17:10 ` Frank Li
2025-06-27 15:33 ` Hans Zhang
2025-06-26 14:50 ` [PATCH v3 05/13] PCI: meson: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 06/13] PCI: armada8k: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 07/13] PCI: bt1: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 08/13] PCI: dw-rockchip: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 09/13] PCI: fu740: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 10/13] PCI: qcom: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 11/13] PCI: qcom-ep: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 12/13] PCI: rcar-gen4: " Hans Zhang
2025-06-26 14:50 ` [PATCH v3 13/13] PCI: tegra194: " Hans Zhang
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=202506280542.6ttkdrur-lkp@intel.com \
--to=lkp@intel.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@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
all inboxes | Powered by JetHome®