From: Adrian Bunk <bunk@stusta.de>
To: David Shaohua Li <shaohua.li@intel.com>, Len Brown <len.brown@intel.com>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error
Date: Wed, 24 Aug 2005 16:44:11 +0200 [thread overview]
Message-ID: <20050824144411.GA4851@stusta.de> (raw)
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 -->
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 reply other threads:[~2005-08-24 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 14:44 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 15:13 2.6.13-rc: ACPI_INTERPRETER=y, PCI=n compile error Brown, Len
2005-08-24 15:30 ` 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=20050824144411.GA4851@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox