From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-devel:devel-athens-arm-201407281729 9/13] ERROR: "dw_pcie_host_init" [drivers/pci/host/pcie-spear13xx.ko] undefined!
Date: Mon, 28 Jul 2014 15:57:18 +0200 [thread overview]
Message-ID: <5266883.bDcz9kd6ee@wuerfel> (raw)
In-Reply-To: <53d65148.2/x780FfPLEYMqov%fengguang.wu@intel.com>
On Monday 28 July 2014 21:34:00 kbuild test robot wrote:
> Hi Wu,
>
> FYI, this happens on a merge commit, which indicates conflicting changes with one of the below merged branches.
>
> 46b7e36 Merge 'arm-soc/for-next' into devel-athens-arm-201407281729
> ed67b70 Merge 'sound/for-next' into devel-athens-arm-201407281729
> df8c9cc Merge 's390/features' into devel-athens-arm-201407281729
> a97b04d Merge 'powerpc/test' into devel-athens-arm-201407281729
> 6baf298 Merge 'powerpc/next' into devel-athens-arm-201407281729
> e216a37 Merge 'tip/sched/core' into devel-athens-arm-201407281729
> 6c9d717 Merge 'tip/perf/core' into devel-athens-arm-201407281729
> ab83da1 Merge 'ath6kl/ath-next-test' into devel-athens-arm-201407281729
> 86fc732 0day base guard for 'devel-athens-arm-201407281729'
> 64aa90f Linux 3.16-rc7
>
>
> tree: git://internal_merge_and_test_tree devel-athens-arm-201407281729
> head: ed9c75e87f52f14597c4db2ba5b45950f2e09c1a
> commit: 46b7e363b2006f212f930aa284b0ad3ca6d3fe48 [9/13] Merge 'arm-soc/for-next' into devel-athens-arm-201407281729
> config: make ARCH=arm allmodconfig
>
> All error/warnings:
>
> >> ERROR: "dw_pcie_host_init" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_handle_msi_irq" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_pcie_msi_init" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_pcie_cfg_write" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_pcie_cfg_read" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_pcie_setup_rc" [drivers/pci/host/pcie-spear13xx.ko] undefined!
> >> ERROR: "dw_pcie_link_up" [drivers/pci/host/pcie-spear13xx.ko] undefined!
I submitted a patch for this already:
http://patchwork.ozlabs.org/patch/373209/
Not sure how to deal with that, as Lucas indicated that it conflicts with
another patch of his. I guess I could just apply my patch as-is to fix the
current bug and let Linus deal with the merge conflict later.
Alternatively, we can turn this driver into builtin-only like some of
the other PCI host controllers. Not as nice, but gets rid of the bug
without introducing a conflict.
Jingoo, Mohit, Bjorn, any other opinions?
Arnd
parent reply other threads:[~2014-07-28 13:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53d65148.2/x780FfPLEYMqov%fengguang.wu@intel.com>]
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=5266883.bDcz9kd6ee@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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