From: Adrian Bunk <bunk@kernel.org>
To: Dipankar Sarma <dipankar@in.ibm.com>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] #if 0 tasklet_kill_immediate()
Date: Tue, 29 Jan 2008 00:12:00 +0200 [thread overview]
Message-ID: <20080128221200.GD8767@does.not.exist> (raw)
This patch #if 0's the no longer used tasklet_kill_immediate().
Signed-off-by: Adrian Bunk <bunk@kernel.org>
---
include/linux/interrupt.h | 1 -
kernel/softirq.c | 3 +++
2 files changed, 3 insertions(+), 1 deletion(-)
06fc93a10822d4e9c53eaa2b4d0a16792305957e
diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index c3db4a0..59d31dc 100644
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -384,7 +384,6 @@ static inline void tasklet_hi_enable(struct tasklet_struct *t)
}
extern void tasklet_kill(struct tasklet_struct *t);
-extern void tasklet_kill_immediate(struct tasklet_struct *t, unsigned int cpu);
extern void tasklet_init(struct tasklet_struct *t,
void (*func)(unsigned long), unsigned long data);
diff --git a/kernel/softirq.c b/kernel/softirq.c
index bd89bc4..0f87c36 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -527,6 +527,8 @@ wait_to_die:
}
#ifdef CONFIG_HOTPLUG_CPU
+
+#if 0
/*
* tasklet_kill_immediate is called to remove a tasklet which can already be
* scheduled for execution on @cpu.
@@ -555,6 +557,7 @@ void tasklet_kill_immediate(struct tasklet_struct *t, unsigned int cpu)
}
BUG();
}
+#endif /* 0 */
static void takeover_tasklets(unsigned int cpu)
{
next reply other threads:[~2008-01-28 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 22:12 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 21:30 [2.6 patch] #if 0 tasklet_kill_immediate() 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=20080128221200.GD8767@does.not.exist \
--to=bunk@kernel.org \
--cc=dipankar@in.ibm.com \
--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