From: Martin Zwickel <martin.zwickel@technotrend.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc3-mm2: compile error in irq.c
Date: Thu, 7 Oct 2004 11:04:50 +0200 [thread overview]
Message-ID: <20041007110450.4fcf9acd@phoebee> (raw)
In-Reply-To: <20041007094404.30a6feb3@phoebee>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Thu, 7 Oct 2004 09:44:04 +0200
Martin Zwickel <martin.zwickel@technotrend.de> bubbled:
> Hi there!
>
> I don't know if someone already made a patch that's working, so I'm
> posting the compile error here:
>
> arch/i386/kernel/irq.c:203: error: redefinition of `is_irq_stack_ptr'
> include/asm/hardirq.h:25: error: `is_irq_stack_ptr' previously defined
> here arch/i386/kernel/irq.c: In function `is_irq_stack_ptr':
> arch/i386/kernel/irq.c:207: error: `hardirq_stack' undeclared (first
> use in this function) arch/i386/kernel/irq.c:207: error: (Each
> undeclared identifier is reported only once
> arch/i386/kernel/irq.c:207: error: for each function it appears in.)
> arch/i386/kernel/irq.c:210: error: `softirq_stack' undeclared (first
> use in this function) make[1]: *** [arch/i386/kernel/irq.o] Error 1
> make: *** [arch/i386/kernel] Error 2
>
Hmm, I made an "#ifdef CONFIG_4KSTACKS" around the is_irq_stack_ptr() in
irq.c because the hardirq_stack() is only defined if the 4K-STACKS are
selected.
Is this the correct way?
--
MyExcuse:
Post-it Note Sludge leaked into the monitor.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-07 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 7:44 2.6.9-rc3-mm2: compile error in irq.c Martin Zwickel
2004-10-07 9:04 ` Martin Zwickel [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=20041007110450.4fcf9acd@phoebee \
--to=martin.zwickel@technotrend.de \
--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 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.