From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6 patch] include/linux/sched.h: no need to guard the normalize_rt_tasks() prototype
Date: Mon, 21 Nov 2005 00:33:47 +0100 [thread overview]
Message-ID: <20051120233347.GP16060@stusta.de> (raw)
There's no need to guard the normalize_rt_tasks() prototype with an
#ifdef CONFIG_MAGIC_SYSRQ.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.15-rc1-mm2-full/include/linux/sched.h.old 2005-11-20 20:44:28.000000000 +0100
+++ linux-2.6.15-rc1-mm2-full/include/linux/sched.h 2005-11-20 20:44:35.000000000 +0100
@@ -1423,12 +1423,8 @@
extern long sched_setaffinity(pid_t pid, cpumask_t new_mask);
extern long sched_getaffinity(pid_t pid, cpumask_t *mask);
-#ifdef CONFIG_MAGIC_SYSRQ
-
extern void normalize_rt_tasks(void);
-#endif
-
#ifdef CONFIG_PM
/*
* Check if a process has been frozen
next reply other threads:[~2005-11-20 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 23:33 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-13 14:58 [2.6 patch] include/linux/sched.h: no need to guard the normalize_rt_tasks() prototype 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=20051120233347.GP16060@stusta.de \
--to=bunk@stusta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox