From: Adrian Bunk <bunk@stusta.de>
To: spyro@f2s.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] include/asm-arm26/hardirq.h: remove #define irq_enter()
Date: Thu, 21 Jul 2005 16:32:34 +0200 [thread overview]
Message-ID: <20050721143234.GE3160@stusta.de> (raw)
This patch removes a #define for irq_enter that is superfluous due to a
similar one in include/linux/hardirq.h .
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Note: The compilation of this patch was not tested.
--- linux-2.6.13-rc3-mm1-full/include/asm-arm26/hardirq.h.old 2005-07-21 16:27:36.000000000 +0200
+++ linux-2.6.13-rc3-mm1-full/include/asm-arm26/hardirq.h 2005-07-21 16:29:32.000000000 +0200
@@ -22,8 +22,6 @@
# error HARDIRQ_BITS is too low!
#endif
-#define irq_enter() (preempt_count() += HARDIRQ_OFFSET)
-
#ifndef CONFIG_SMP
extern asmlinkage void __do_softirq(void);
next reply other threads:[~2005-07-21 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 14:32 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-31 18:29 [2.6 patch] include/asm-arm26/hardirq.h: remove #define irq_enter() 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=20050721143234.GE3160@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spyro@f2s.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