From: Dave Young <hidave.darkstar@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ulrich Drepper <drepper@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Roland McGrath <roland@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
James Morris <jmorris@namei.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 02/18] sysctl extern cleanup - signal
Date: Sat, 20 Feb 2010 22:07:44 +0800 [thread overview]
Message-ID: <20100220140744.GA3195@darkstar> (raw)
Extern declarations in sysctl.c should be move to their own head file,
and then include them in relavant .c files.
Move print_fatal_signals extern declaration to linux/signal.h
Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
---
include/linux/signal.h | 3 +++
kernel/sysctl.c | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
--- linux-2.6.32.orig/include/linux/signal.h 2010-02-20 14:02:28.674925069 +0800
+++ linux-2.6.32/include/linux/signal.h 2010-02-20 14:06:02.014905163 +0800
@@ -7,6 +7,9 @@
#ifdef __KERNEL__
#include <linux/list.h>
+#ifdef CONFIG_SYSCTL
+extern int print_fatal_signals;
+#endif
/*
* Real Time signals may be queued.
*/
--- linux-2.6.32.orig/kernel/sysctl.c 2010-02-20 14:03:41.452418032 +0800
+++ linux-2.6.32/kernel/sysctl.c 2010-02-20 14:05:17.149075410 +0800
@@ -54,6 +54,7 @@
#include <linux/slow-work.h>
#include <linux/perf_event.h>
#include <linux/rcustring.h>
+#include <linux/signal.h>
#include <asm/uaccess.h>
#include <asm/processor.h>
@@ -68,7 +69,6 @@
#if defined(CONFIG_SYSCTL)
/* External variables not in a header file. */
-extern int print_fatal_signals;
extern int max_threads;
extern int core_uses_pid;
extern int suid_dumpable;
reply other threads:[~2010-02-20 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100220140744.GA3195@darkstar \
--to=hidave.darkstar@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.