From: Niklas Cassel <cassel@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-pci@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Subject: Re: [pci:controller/rockchip 11/11] drivers/pci/controller/dwc/pcie-dw-rockchip.c:491:undefined reference to `pci_epc_init_notify'
Date: Thu, 27 Jun 2024 10:33:24 +0200 [thread overview]
Message-ID: <Zn0j1LrkLELW0fO1@ryzen.lan> (raw)
In-Reply-To: <202406270721.a8SQi2hn-lkp@intel.com>
On Thu, Jun 27, 2024 at 07:54:05AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git controller/rockchip
> head: 246afbe0f6fca433d8d918b740719170b1b082cc
> commit: 246afbe0f6fca433d8d918b740719170b1b082cc [11/11] PCI: dw-rockchip: Use pci_epc_init_notify() directly
> config: loongarch-randconfig-r081-20240626 (https://download.01.org/0day-ci/archive/20240627/202406270721.a8SQi2hn-lkp@intel.com/config)
> compiler: loongarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240627/202406270721.a8SQi2hn-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/202406270721.a8SQi2hn-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.o: in function `dw_pcie_ep_init_notify':
> drivers/pci/controller/dwc/pcie-designware-ep.c:26:(.text+0x1e4): undefined reference to `pci_epc_init_notify'
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.o: in function `dw_pcie_ep_deinit':
> drivers/pci/controller/dwc/pcie-designware-ep.c:640:(.text+0x83c): undefined reference to `pci_epc_mem_free_addr'
> 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.o: in function `dw_pcie_ep_linkup':
> drivers/pci/controller/dwc/pcie-designware-ep.c:811:(.text+0x924): undefined reference to `pci_epc_linkup'
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.o: in function `dw_pcie_ep_linkdown':
> drivers/pci/controller/dwc/pcie-designware-ep.c:836:(.text+0x964): undefined reference to `pci_epc_linkdown'
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.o: in function `dw_pcie_ep_init':
> 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: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'
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-designware-ep.c:906:(.text+0xf74): undefined reference to `pci_epc_mem_exit'
> loongarch64-linux-ld: drivers/pci/controller/dwc/pcie-dw-rockchip.o: in function `rockchip_pcie_configure_ep':
> >> drivers/pci/controller/dwc/pcie-dw-rockchip.c:491:(.text+0x7cc): undefined reference to `pci_epc_init_notify'
Hello Krzysztof,
This is the same problem that the kernel test robot previously reported,
and is fixed by:
https://lore.kernel.org/linux-pci/20240626191325.4074794-2-cassel@kernel.org/
Like I wrote in the other kernel test robot report, depending on .config,
we could also see another build error if we don't have:
7a847796e509 ("PCI: endpoint: Introduce 'epc_deinit' event and notify the EPF drivers")
(from the pci/endpoint branch).
You have also previously cherry-picked:
3d2e425263e2 ("PCI: dwc: ep: Add a generic dw_pcie_ep_linkdown() API to handle Link Down event")
(from the pci/controller/dwc branch) which we also depend on.
Perhaps the smartest thing right now is to just recreate the
pci/controller/rockchip branch, by:
1) reset the rockchip branch to v6.10-rc1
2) merge the pci/controller/dwc branch to the rockchip branch
3) merge the pci/endpoint branch to to the rockchip branch
4) pick all the patches that are currently on the pci/controller/rockchip
5) squash: 246afbe0f6fc ("PCI: dw-rockchip: Use pci_epc_init_notify() directly")
into the commit that adds dw-rockchip endpoint mode support
(9b2ba393b3a6 ("PCI: dw-rockchip: Add endpoint mode support"))
6) squash: https://lore.kernel.org/linux-pci/20240626191325.4074794-2-cassel@kernel.org/
into the commit that adds dw-rockchip endpoint mode support
(9b2ba393b3a6 ("PCI: dw-rockchip: Add endpoint mode support"))
This way:
- All commits will build as individual patches, so no build errors from the
test robot (even when it builds a patch that is in the middle (e.g. 10/11)).
- Even if futher commits are applied to pci/controller/dwc or pci/endpoint,
we will not depend on any newly applied patches to these branches, so there
will be no need to "re-merge" the branches to the rockchip branch.
Kind regards,
Niklas
next prev parent reply other threads:[~2024-06-27 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 23:54 [pci:controller/rockchip 11/11] drivers/pci/controller/dwc/pcie-dw-rockchip.c:491:undefined reference to `pci_epc_init_notify' kernel test robot
2024-06-27 8:33 ` Niklas Cassel [this message]
2024-06-27 8:51 ` Niklas Cassel
2024-06-28 0:27 ` Krzysztof Wilczyński
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=Zn0j1LrkLELW0fO1@ryzen.lan \
--to=cassel@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@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.