From: Bjorn Helgaas <helgaas@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Keith Busch <kbusch@kernel.org>,
kbuild-all@01.org, linux-pci@vger.kernel.org
Subject: Re: [pci:for-linus 7/7] portdrv_pci.c:undefined reference to `pcie_bandwidth_notification_init'
Date: Wed, 1 May 2019 15:33:06 -0500 [thread overview]
Message-ID: <20190501203306.GB47079@google.com> (raw)
In-Reply-To: <201905020410.fUt0VDkK%lkp@intel.com>
On Thu, May 02, 2019 at 04:19:13AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git for-linus
> head: 302b77157e6689d047d9e668ad1aadfa7a267940
> commit: 302b77157e6689d047d9e668ad1aadfa7a267940 [7/7] PCI/LINK: Add Kconfig option (default off)
> config: i386-defconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> git checkout 302b77157e6689d047d9e668ad1aadfa7a267940
> # save the attached .config to linux build tree
> make ARCH=i386
302b77157e66 was the first version of the patch, which I speculatively
applied before Keith's ack. I've already replaced it with his v2 patch,
which should fix this issue, so no action needed AFAIK.
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> ld: drivers/pci/pcie/portdrv_pci.o: in function `pcie_portdrv_init':
> >> portdrv_pci.c:(.init.text+0x78): undefined reference to `pcie_bandwidth_notification_init'
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2019-05-01 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 20:19 [pci:for-linus 7/7] portdrv_pci.c:undefined reference to `pcie_bandwidth_notification_init' kbuild test robot
2019-05-01 20:33 ` Bjorn Helgaas [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=20190501203306.GB47079@google.com \
--to=helgaas@kernel.org \
--cc=kbuild-all@01.org \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.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