From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: linux-next: Tree for May 6 (acpi: PCI=n) Date: Thu, 06 May 2010 16:29:42 -0400 (EDT) Message-ID: References: <20100506151502.f97afe54.sfr@canb.auug.org.au> <20100506080722.3b724475.randy.dunlap@oracle.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from vms173019pub.verizon.net ([206.46.173.19]:36231 "EHLO vms173019pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758851Ab0EFU3r (ORCPT ); Thu, 6 May 2010 16:29:47 -0400 In-reply-to: <20100506080722.3b724475.randy.dunlap@oracle.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Randy Dunlap Cc: Stephen Rothwell , linux-acpi@vger.kernel.org, linux-next@vger.kernel.org, LKML > When CONFIG_PCI is not enabled: > > arch/x86/kernel/acpi/boot.c:1034: error: 'pci_bus_type' undeclared > > drivers/acpi/reboot.c:30: error:implicit declaration of function 'pci_find_bus' > drivers/acpi/reboot.c:30: warning: assignment makes pointer from integer without a cast > drivers/acpi/reboot.c:38: error:implicit declaration of function 'pci_bus_write_config_byte' CONFIG_ACPI depends on CONFIG_PCI, so this file should not be build with CONFIG_PCI=n. Please let me know how you were able to generate this illegal configuration. thanks, Len Brown, Intel Open Source Technology Center