public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Krzysztof Wilczyński " <kwilczynski@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: [pci:controller/rockchip] BUILD REGRESSION 246afbe0f6fca433d8d918b740719170b1b082cc
Date: Thu, 27 Jun 2024 04:40:02 +0800	[thread overview]
Message-ID: <202406270459.JXtYsIVE-lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git controller/rockchip
branch HEAD: 246afbe0f6fca433d8d918b740719170b1b082cc  PCI: dw-rockchip: Use pci_epc_init_notify() directly

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202406270250.k2esVVnL-lkp@intel.com

Error/Warning: (recently discovered and may have been fixed)

drivers/pci/controller/dwc/pcie-designware-ep.c:26:(.text+0x1e4): undefined reference to `pci_epc_init_notify'
drivers/pci/controller/dwc/pcie-designware-ep.c:640:(.text+0x83c): undefined reference to `pci_epc_mem_free_addr'
drivers/pci/controller/dwc/pcie-designware-ep.c:811:(.text+0x924): undefined reference to `pci_epc_linkup'
drivers/pci/controller/dwc/pcie-designware-ep.c:836:(.text+0x964): undefined reference to `pci_epc_linkdown'
drivers/pci/controller/dwc/pcie-designware-ep.c:875:(.text+0xe90): undefined reference to `__devm_pci_epc_create'
loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.c:643:(.text+0x854): undefined reference to `pci_epc_mem_exit'
loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.c:888:(.text+0xf20): undefined reference to `pci_epc_mem_init'
loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.c:895:(.text+0xf54): undefined reference to `pci_epc_mem_alloc_addr'

Error/Warning ids grouped by kconfigs:

recent_errors
`-- loongarch-randconfig-r081-20240626
    |-- drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-__devm_pci_epc_create
    |-- drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_init_notify
    |-- drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_linkdown
    |-- drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_linkup
    |-- drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_mem_free_addr
    |-- loongarch64-linux-ld:drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_mem_alloc_addr
    |-- loongarch64-linux-ld:drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_mem_exit
    `-- loongarch64-linux-ld:drivers-pci-controller-dwc-pcie-designware-ep.c:(.text):undefined-reference-to-pci_epc_mem_init

elapsed time: 6017m

configs tested: 41
configs skipped: 0

tested configs:
arc                   randconfig-001-20240623   gcc-13.2.0
arc                   randconfig-002-20240623   gcc-13.2.0
arm                   randconfig-001-20240623   gcc-13.2.0
arm                   randconfig-002-20240623   gcc-13.2.0
arm                   randconfig-003-20240623   gcc-13.2.0
arm                   randconfig-004-20240623   gcc-13.2.0
csky                  randconfig-001-20240623   gcc-13.2.0
csky                  randconfig-002-20240623   gcc-13.2.0
i386         buildonly-randconfig-004-20240623   gcc-13
i386                  randconfig-001-20240623   gcc-9
i386                  randconfig-003-20240623   gcc-13
i386                  randconfig-005-20240623   gcc-7
i386                  randconfig-012-20240623   gcc-8
i386                  randconfig-015-20240623   gcc-8
loongarch             randconfig-001-20240623   gcc-13.2.0
loongarch             randconfig-002-20240623   gcc-13.2.0
nios2                 randconfig-001-20240623   gcc-13.2.0
nios2                 randconfig-002-20240623   gcc-13.2.0
parisc                randconfig-001-20240623   gcc-13.2.0
parisc                randconfig-002-20240623   gcc-13.2.0
powerpc               randconfig-001-20240623   gcc-13.2.0
powerpc64             randconfig-001-20240623   gcc-13.2.0
powerpc64             randconfig-003-20240623   gcc-13.2.0
s390                  randconfig-001-20240623   gcc-13.2.0
s390                  randconfig-002-20240623   gcc-13.2.0
sh                    randconfig-001-20240623   gcc-13.2.0
sh                    randconfig-002-20240623   gcc-13.2.0
sparc64               randconfig-001-20240623   gcc-13.2.0
sparc64               randconfig-002-20240623   gcc-13.2.0
um                    randconfig-001-20240623   gcc-7
x86_64                randconfig-001-20240623   gcc-13
x86_64                randconfig-002-20240623   gcc-13
x86_64                randconfig-004-20240623   gcc-13
x86_64                randconfig-005-20240623   gcc-8
x86_64                randconfig-012-20240623   gcc-13
x86_64                randconfig-015-20240623   gcc-13
x86_64                randconfig-071-20240623   gcc-13
x86_64                randconfig-072-20240623   gcc-13
x86_64                randconfig-075-20240623   gcc-13
xtensa                randconfig-001-20240623   gcc-13.2.0
xtensa                randconfig-002-20240623   gcc-13.2.0

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

                 reply	other threads:[~2024-06-26 20:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202406270459.JXtYsIVE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.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