From: Adrian Bunk <bunk@stusta.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
Date: Wed, 24 Aug 2005 17:30:13 +0200 [thread overview]
Message-ID: <20050824153012.GC4851@stusta.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B30046956FE@hdsmsx401.amr.corp.intel.com>
On Wed, Aug 24, 2005 at 11:13:05AM -0400, Brown, Len wrote:
>
> >Subject: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
> >
> >I got the following compile error in 2.6.13-rc6-mm2, but it
> >seems to be
> >a problem coming from Linus' tree introduced by the
> > [ACPI] S3 resume: avoid kmalloc() might_sleep oops symptom
> >patch:
> >
> ><-- snip -->
> >
> >...
> > LD .tmp_vmlinux1
> >drivers/built-in.o: In function `acpi_os_allocate':
> >: undefined reference to `acpi_in_resume'
> >make: *** [.tmp_vmlinux1] Error 1
> >
> ><-- snip -->
>
> Do you have an ACPI-enabled machine that has no PCI?
> I'm not aware of any, and would be interested to know
> if one exists.
No, I don't have one.
> We've had problems with this theoretical build config
> for some time:
> http://bugzilla.kernel.org/show_bug.cgi?id=1364
> because nobody, including me, tests it.
>
> Indeed, one possible fix would be to make CONFIG_ACPI
> depend on CONFIG_PCI -- which brings me back to
> my origianl question.
Making ACPI dependent on PCI is a possible solution for this problem.
> -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
next prev parent reply other threads:[~2005-08-24 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 15:13 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error Brown, Len
2005-08-24 15:13 ` Brown, Len
2005-08-24 15:30 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 14:44 Adrian Bunk
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=20050824153012.GC4851@stusta.de \
--to=bunk@stusta.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.