linux-kernel - [PATCH 55/58] sched: Add prototype for sched_set_stop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1353302917-13995-56-git-send-email-josh@joshtriplett.org>
Date:	Sun, 18 Nov 2012 21:28:34 -0800
From:	Josh Triplett <josh@...htriplett.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org
Cc:	Josh Triplett <josh@...htriplett.org>
Subject: [PATCH 55/58] sched: Add prototype for sched_set_stop_task

kernel/sched/core.c defines a function sched_set_stop_task, only
referenced from kernel/stop_machine.c via an extern declaration; no
header file defines a prototype for sched_set_stop_task.  Add a
prototype right before its definition, to satisfy GCC
(-Wmissing-prototypes) and Sparse (-Wdecl).

kernel/sched/core.c:803:6: warning: no previous prototype for ‘sched_set_stop_task’ [-Wmissing-prototypes]

Signed-off-by: Josh Triplett <josh@...htriplett.org>
---
 kernel/sched/core.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 2d8927f..2d2f5a4 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -800,6 +800,8 @@ static void update_rq_clock_task(struct rq *rq, s64 delta)
 #endif
 }
 
+void sched_set_stop_task(int cpu, struct task_struct *stop);
+
 void sched_set_stop_task(int cpu, struct task_struct *stop)
 {
 	struct sched_param param = { .sched_priority = MAX_RT_PRIO - 1 };
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/