From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jesse Barnes <jbarnes@virtuousgeek•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Rafael J. Wysocki" <rjw@sisk•pl>
Subject: linux-next: build failure after merge of the final tree (pci-current tree related)
Date: Wed, 25 Aug 2010 11:56:04 +1000 [thread overview]
Message-ID: <20100825115604.07928f97.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi Jesse,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/pci/hotplug/pciehp_core.c: In function 'pciehp_probe':
drivers/pci/hotplug/pciehp_core.c:238: error: implicit declaration of function 'pciehp_acpi_slot_detection_check'
Caused by commit 28eb5f274a305bf3a13b2c80c4804d4515d05c64 ("PCI: PCIe:
Ask BIOS for control of all native services at once"). This function is
only declared if CONFIG_ACPI is defined.
I have reverted that commit for today (and the two that interact with it:
2bd50dd800b52245294cfceb56be62020cdc7515 "PCI: PCIe: Disable PCIe port
services during port initialization" and
271fb719cc472af3b1e96d8c527bb0da7060a172 "PCI: PCIe: Move PCIe PME code
to the pcie directory").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-08-25 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 1:56 Stephen Rothwell [this message]
2010-08-25 19:33 ` linux-next: build failure after merge of the final tree (pci-current tree related) Rafael J. Wysocki
2010-08-25 19:54 ` Jesse Barnes
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=20100825115604.07928f97.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@sisk$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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