linux-kernel - [PATCH -mm 07/17] sysctl extern cleanup

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>] [day] [month] [year] [list]

Message-ID: <20100221142351.GA3008@darkstar>
Date:	Sun, 21 Feb 2010 22:23:51 +0800
From:	Dave Young <hidave.darkstar@...il.com>
To:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	James Morris <jmorris@...ei.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH -mm 07/17] sysctl extern cleanup - latencytop

Extern declarations in sysctl.c should be move to their own head file,
and then include them in relavant .c files.

latencytop_enabled is declcared in linux/latencytop.h, so remove the
declaration in sysctl.c, include the head file instead.

Signed-off-by: Dave Young <hidave.darkstar@...il.com>
---
 kernel/sysctl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6.32.orig/kernel/sysctl.c	2010-02-21 09:55:08.013076578 +0800
+++ linux-2.6.32/kernel/sysctl.c	2010-02-21 09:57:19.646397324 +0800
@@ -58,6 +58,7 @@
 #include <linux/binfmts.h>
 #include <linux/pid.h>
 #include <linux/compat.h>
+#include <linux/latencytop.h>
 
 #include <asm/uaccess.h>
 #include <asm/processor.h>
@@ -73,7 +74,6 @@
 
 /* External variables not in a header file. */
 extern int max_threads;
-extern int latencytop_enabled;
 extern int sysctl_nr_open_min, sysctl_nr_open_max;
 #ifdef CONFIG_RCU_TORTURE_TEST
 extern int rcutorture_runnable;
--
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/