From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: [2.6 patch] kernel/capability.c: make a spinlock static
Date: Mon, 17 Jan 2005 09:13:47 +0100 [thread overview]
Message-ID: <20050117081347.GB4274@stusta.de> (raw)
This patch makes a needlessly global spinlock static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Chris Wright <chrisw@osdl.org>
---
diffstat output:
include/linux/capability.h | 2 --
kernel/capability.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/include/linux/capability.h.old 2004-12-12 02:43:59.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/include/linux/capability.h 2004-12-12 02:44:05.000000000 +0100
@@ -44,8 +44,6 @@
#include <linux/spinlock.h>
-extern spinlock_t task_capability_lock;
-
/* #define STRICT_CAP_T_TYPECHECKS */
#ifdef STRICT_CAP_T_TYPECHECKS
--- linux-2.6.10-rc2-mm4-full/kernel/capability.c.old 2004-12-12 02:43:23.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/kernel/capability.c 2004-12-12 02:43:45.000000000 +0100
@@ -20,10 +20,10 @@
EXPORT_SYMBOL(cap_bset);
/*
- * This global lock protects task->cap_* for all tasks including current.
+ * This lock protects task->cap_* for all tasks including current.
* Locking rule: acquire this prior to tasklist_lock.
*/
-DEFINE_SPINLOCK(task_capability_lock);
+static DEFINE_SPINLOCK(task_capability_lock);
/*
* For sys_getproccap() and sys_setproccap(), any of the three
next reply other threads:[~2005-01-17 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 8:13 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-12 19:16 [2.6 patch] kernel/capability.c: make a spinlock static Adrian Bunk
2004-12-13 19:40 ` Chris Wright
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=20050117081347.GB4274@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=chrisw@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