From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [pci:bug/kbz46481 2/2] (.text+0x17196): undefined reference to `bh_check_bridge'
Date: Sun, 14 Oct 2012 02:24:57 +0000 [thread overview]
Message-ID: <20121014022457.GA6795@localhost> (raw)
Hi Bjorn,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git bug/kbz46481
head: 54a2804aaa64648d842486ec49237583b198b41c
commit: 54a2804aaa64648d842486ec49237583b198b41c [2/2] debug
config: x86_64-allmodconfig # make ARCH=x86_64
branch date: 3 days ago
commit date: 3 days ago
All error/warnings:
drivers/built-in.o: In function `pci_create_slot':
(.text+0x17196): undefined reference to `bh_check_bridge'
drivers/built-in.o: In function `pci_create_slot':
(.text+0x1730d): undefined reference to `bh_check_bridge'
drivers/built-in.o: In function `pci_create_slot':
(.text+0x173f3): undefined reference to `bh_check_bridge'
drivers/built-in.o: In function `pci_create_slot':
(.text+0x1749d): undefined reference to `bh_check_bridge'
drivers/built-in.o: In function `pci_create_slot':
(.text+0x1752e): undefined reference to `bh_check_bridge'
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-14 2:24 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=20121014022457.GA6795@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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).