From: kbuild test robot <fengguang.wu@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: kbuild-all@01.org, linux-pci@vger.kernel.org
Subject: [pci:pci/host-iproc 19/20] drivers/pci/host/pcie-iproc.c:526:29: error: 'iproc' undeclared
Date: Wed, 12 Oct 2016 06:06:49 +0800 [thread overview]
Message-ID: <201610120622.cxSCDDk2%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/host-iproc
head: 8c662a9ee7a7ff860f0ffc4935b960d90c766a18
commit: 99de075c313a49110295a3ba71d08300c4690229 [19/20] PCI: iproc: Add local struct device pointers
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 99de075c313a49110295a3ba71d08300c4690229
# save the attached .config to linux build tree
make.cross ARCH=arm64
All errors (new ones prefixed by >>):
drivers/pci/host/pcie-iproc.c: In function 'iproc_pcie_setup':
>> drivers/pci/host/pcie-iproc.c:526:29: error: 'iproc' undeclared (first use in this function)
if (iproc_pcie_msi_enable(iproc))
^~~~~
drivers/pci/host/pcie-iproc.c:526:29: note: each undeclared identifier is reported only once for each function it appears in
vim +/iproc +526 drivers/pci/host/pcie-iproc.c
520 goto err_rm_root_bus;
521 }
522
523 iproc_pcie_enable(iproc_pcie);
524
525 if (IS_ENABLED(CONFIG_PCI_MSI))
> 526 if (iproc_pcie_msi_enable(iproc))
527 dev_info(dev, "not using iProc MSI\n");
528
529 pci_scan_child_bus(bus);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30681 bytes --]
reply other threads:[~2016-10-11 22:07 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=201610120622.cxSCDDk2%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=bhelgaas@google.com \
--cc=kbuild-all@01.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;
as well as URLs for NNTP newsgroup(s).