From: Adrian Bunk <adrian.bunk@stusta.de>
To: Ed Sweetman <safemode@comcast.net>
Cc: Norbert Preining <preining@logic.at>, Ed Tomlinson <edt@aei.ca>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc3-mm1 build failure
Date: Mon, 4 Oct 2004 01:26:31 +0200 [thread overview]
Message-ID: <20041003232631.GV1948@stusta.mhn.de> (raw)
In-Reply-To: <416084A5.4080200@comcast.net>
On Sun, Oct 03, 2004 at 07:00:53PM -0400, Ed Sweetman wrote:
> None of the mails reporting that inserting a header in any file has
> produced a build here that actually gets rid of the build error. I have
> the same errors about implicit declarations of ack_APIC_irq that i had
> before i added asm/io_apic.h to irq.c in arch/i386/kernel and before i
> added it to include/asm/hardirq.h. I've attached my .config to see if
> anyone realizes what i'm doing wrong or what's not being defined
> correctly. thanks.
You have to include asm/apic.h in hardirq.h (not asm/io_apic.h).
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:[~2004-10-03 23:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 9:16 2.6.9-rc3-mm1 build failure Norbert Preining
2004-10-02 9:29 ` Andrew Morton
2004-10-02 10:33 ` Norbert Preining
2004-10-02 10:50 ` Adrian Bunk
2004-10-02 10:58 ` Tim Cambrant
2004-10-02 13:01 ` Ed Sweetman
2004-10-02 16:54 ` Adrian Bunk
2004-10-03 8:30 ` Norbert Preining
2004-10-03 23:00 ` Ed Sweetman
2004-10-03 23:24 ` Andrew Morton
2004-10-04 0:13 ` Adrian Bunk
2004-10-03 23:26 ` Adrian Bunk [this message]
2004-10-02 18:40 ` Ed Tomlinson
2004-10-02 23:03 ` Ed Tomlinson
2004-10-03 7:14 ` Jeremy Fitzhardinge
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=20041003232631.GV1948@stusta.mhn.de \
--to=adrian.bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=edt@aei.ca \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
--cc=safemode@comcast.net \
/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.