From: Randy Dunlap <randy.dunlap@oracle.com>
To: Len Brown <lenb@kernel.org>, James Morris <jmorris@namei.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-acpi@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 6 (acpi: PCI=n)
Date: Thu, 6 May 2010 13:42:11 -0700 [thread overview]
Message-ID: <20100506134211.e08c795a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005061628070.12696@localhost.localdomain>
On Thu, 06 May 2010 16:29:42 -0400 (EDT) Len Brown wrote:
> > 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.
Same TPM kconfig that selects ACPI without any other qualifications.
In 50 randconfig builds, 12 build failures were due to that one bad kconfig.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-05-06 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100506151502.f97afe54.sfr@canb.auug.org.au>
2010-05-06 15:05 ` linux-next: Tree for May 6 (acpi: PM=n) Randy Dunlap
2010-05-06 20:26 ` [linux-pm] " Len Brown
2010-05-06 20:32 ` Randy Dunlap
2010-05-06 23:27 ` James Morris
2010-05-06 23:38 ` Randy Dunlap
2010-05-06 15:07 ` linux-next: Tree for May 6 (acpi: PCI=n) Randy Dunlap
2010-05-06 20:29 ` Len Brown
2010-05-06 20:42 ` Randy Dunlap [this message]
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=20100506134211.e08c795a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jmorris@namei.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).