public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: akpm@osdl.org, acpi-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 5/9] ACPI should depend on, not select PCI
Date: Sun, 4 Dec 2005 17:09:20 +0100	[thread overview]
Message-ID: <20051204160920.GS31395@stusta.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300549CF57@hdsmsx401.amr.corp.intel.com>

On Wed, Nov 30, 2005 at 08:58:22PM -0500, Brown, Len wrote:

> No, I can't apply this -- it allows
> Kconfig to create IA64 configs without PCI,
> which do not build.
> 
> there must be a better way.

According to arch/ia64/Kconfig, PCI support is optional on ia64.

Either arch/ia64/Kconfig should be fixed or the PCI=n builds must be 
fixed on ia64.

Looking closer, is the problem you are talking about caused by the fact 
that IA64_GENERIC select's options without ensuring that the 
dependencies of what it is select'ing are fulfilled?

> -Len 

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

  parent reply	other threads:[~2005-12-04 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01  1:58 [patch 5/9] ACPI should depend on, not select PCI Brown, Len
2005-12-01 10:00 ` Roman Zippel
2005-12-04 16:09 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-28 21:59 akpm-3NddpPZAyC0

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=20051204160920.GS31395@stusta.de \
    --to=bunk@stusta.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@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