From: Adrian Bunk <bunk@stusta.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@lst.de>,
ak@suse.de, discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: [2.6 patch] x86_64 hardirq.h: no need to #ifdef CONFIG_X86
Date: Wed, 24 Nov 2004 01:19:42 +0100 [thread overview]
Message-ID: <20041124001941.GF2927@stusta.de> (raw)
I can't see any reason for the #ifdef CONFIG_X86 introduced to the
x86_64 hardirq.h as part of the generic irq subsystem changes.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.10-rc2-mm3-full/include/asm-x86_64/hardirq.h.old 2004-11-23 23:18:20.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/include/asm-x86_64/hardirq.h 2004-11-23 23:18:35.000000000 +0100
@@ -21,7 +21,6 @@
*/
static inline void ack_bad_irq(unsigned int irq)
{
-#ifdef CONFIG_X86
printk("unexpected IRQ trap at vector %02x\n", irq);
#ifdef CONFIG_X86_LOCAL_APIC
/*
@@ -34,6 +33,5 @@
*/
ack_APIC_irq();
#endif
-#endif
}
#endif /* __ASM_HARDIRQ_H */
next reply other threads:[~2004-11-24 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 0:19 Adrian Bunk [this message]
2004-11-24 10:40 ` [2.6 patch] x86_64 hardirq.h: no need to #ifdef CONFIG_X86 Andi Kleen
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=20041124001941.GF2927@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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