From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] kernel/sys.c: make some code static
Date: Tue, 25 Jan 2005 08:49:17 +0100 [thread overview]
Message-ID: <20050125074917.GH3515@stusta.de> (raw)
This patch makes some needlessly global code static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
kernel/signal.c | 2 --
kernel/sys.c | 4 ++--
2 files changed, 2 insertions(+), 4 deletions(-)
This patch was already sent on:
- 12 Dec 2004
--- linux-2.6.10-rc2-mm4-full/kernel/sys.c.old 2004-12-12 03:18:40.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/kernel/sys.c 2004-12-12 03:19:19.000000000 +0100
@@ -90,7 +90,7 @@
*/
static struct notifier_block *reboot_notifier_list;
-DEFINE_RWLOCK(notifier_lock);
+static DEFINE_RWLOCK(notifier_lock);
/**
* notifier_chain_register - Add notifier to a notifier chain
@@ -1544,7 +1544,7 @@
* given child after it's reaped, or none so this sample is before reaping.
*/
-void k_getrusage(struct task_struct *p, int who, struct rusage *r)
+static void k_getrusage(struct task_struct *p, int who, struct rusage *r)
{
struct task_struct *t;
unsigned long flags;
--- linux-2.6.10-rc2-mm4-full/kernel/signal.c.old 2004-12-12 03:18:25.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/kernel/signal.c 2004-12-12 03:18:32.000000000 +0100
@@ -27,8 +27,6 @@
#include <asm/unistd.h>
#include <asm/siginfo.h>
-extern void k_getrusage(struct task_struct *, int, struct rusage *);
-
/*
* SLAB caches for signal bits.
*/
next reply other threads:[~2005-01-25 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 7:49 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-12 20:01 [2.6 patch] kernel/sys.c: make some code static 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=20050125074917.GH3515@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--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