From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, hpa@zytor.com
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
neilb@cse.unsw.edu.au, linux-raid@vger.kernel.org
Subject: [-mm patch] make variables static after klibc merge
Date: Mon, 26 Jun 2006 22:56:29 +0200 [thread overview]
Message-ID: <20060626205629.GE23314@stusta.de> (raw)
We can now make the following variables static:
- drivers/md/md.c: mdp_major
- init/main.c: envp_init[]
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
This patch was already sent on:
- 16 May 2006
drivers/md/md.c | 2 +-
init/main.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.17-rc4-mm1-full/drivers/md/md.c.old 2006-05-16 12:49:59.000000000 +0200
+++ linux-2.6.17-rc4-mm1-full/drivers/md/md.c 2006-05-16 12:50:17.000000000 +0200
@@ -2563,7 +2563,7 @@
.default_attrs = md_default_attrs,
};
-int mdp_major = 0;
+static int mdp_major = 0;
static struct kobject *md_probe(dev_t dev, int *part, void *data)
{
--- linux-2.6.17-rc4-mm1-full/init/main.c.old 2006-05-16 13:20:22.000000000 +0200
+++ linux-2.6.17-rc4-mm1-full/init/main.c 2006-05-16 13:20:43.000000000 +0200
@@ -161,7 +161,7 @@
__setup("maxcpus=", maxcpus);
static char * argv_init[MAX_INIT_ARGS+2] = { "init", NULL, };
-char * envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
+static char * envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
static const char *panic_later, *panic_param;
extern struct obs_kernel_param __setup_start[], __setup_end[];
next reply other threads:[~2006-06-26 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 20:56 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 7:56 2.6.17-rc4-mm1 Andrew Morton
2006-05-16 12:32 ` [-mm patch] make variables static after klibc merge 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=20060626205629.GE23314@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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.