From: Adrian Bunk <bunk@stusta.de>
To: Dipankar Sarma <dipankar@in.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] kernel/rcupdate.c: make two structs static
Date: Thu, 12 Jan 2006 11:48:03 +0100 [thread overview]
Message-ID: <20060112104803.GQ29663@stusta.de> (raw)
This patch makes two needlessly global structs static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
include/linux/rcupdate.h | 2 --
kernel/rcupdate.c | 4 ++--
2 files changed, 2 insertions(+), 4 deletions(-)
--- linux-2.6.15-mm3-full/include/linux/rcupdate.h.old 2006-01-12 02:23:35.000000000 +0100
+++ linux-2.6.15-mm3-full/include/linux/rcupdate.h 2006-01-12 01:06:47.000000000 +0100
@@ -109,8 +109,6 @@
DECLARE_PER_CPU(struct rcu_data, rcu_data);
DECLARE_PER_CPU(struct rcu_data, rcu_bh_data);
-extern struct rcu_ctrlblk rcu_ctrlblk;
-extern struct rcu_ctrlblk rcu_bh_ctrlblk;
/*
* Increment the quiescent state counter.
--- linux-2.6.15-mm3-full/kernel/rcupdate.c.old 2006-01-12 01:06:54.000000000 +0100
+++ linux-2.6.15-mm3-full/kernel/rcupdate.c 2006-01-12 01:07:07.000000000 +0100
@@ -49,13 +49,13 @@
#include <linux/cpu.h>
/* Definition for rcupdate control block. */
-struct rcu_ctrlblk rcu_ctrlblk = {
+static struct rcu_ctrlblk rcu_ctrlblk = {
.cur = -300,
.completed = -300,
.lock = SPIN_LOCK_UNLOCKED,
.cpumask = CPU_MASK_NONE,
};
-struct rcu_ctrlblk rcu_bh_ctrlblk = {
+static struct rcu_ctrlblk rcu_bh_ctrlblk = {
.cur = -300,
.completed = -300,
.lock = SPIN_LOCK_UNLOCKED,
next reply other threads:[~2006-01-12 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 10:48 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-22 13:54 [2.6 patch] kernel/rcupdate.c: make two structs 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=20060112104803.GQ29663@stusta.de \
--to=bunk@stusta.de \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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