public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] arch/i386/kernel/cpu/: make tons of functions static
Date: Fri, 3 Feb 2006 22:12:27 +0100	[thread overview]
Message-ID: <20060203211227.GO4408@stusta.de> (raw)
In-Reply-To: <20060203000704.3964a39f.akpm@osdl.org>

On Fri, Feb 03, 2006 at 12:07:04AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm4:
>...
> +i386-cpu-hotplug-dont-access-freed-memory.patch
> 
>  init sectoin fix
>...


Functions only used in the files they are defined in should be static.


Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 arch/i386/kernel/cpu/amd.c       |    2 +-
 arch/i386/kernel/cpu/centaur.c   |    2 +-
 arch/i386/kernel/cpu/cyrix.c     |    4 ++--
 arch/i386/kernel/cpu/nexgen.c    |    2 +-
 arch/i386/kernel/cpu/rise.c      |    2 +-
 arch/i386/kernel/cpu/transmeta.c |    2 +-
 arch/i386/kernel/cpu/umc.c       |    2 +-
 7 files changed, 8 insertions(+), 8 deletions(-)

--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/amd.c.old	2006-02-03 16:14:11.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/amd.c	2006-02-03 16:14:24.000000000 +0100
@@ -283,7 +283,7 @@
 
 //early_arch_initcall(amd_init_cpu);
 
-int __init amd_exit_cpu(void)
+static int __init amd_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_AMD] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/centaur.c.old	2006-02-03 16:14:32.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/centaur.c	2006-02-03 16:14:42.000000000 +0100
@@ -471,7 +471,7 @@
 
 //early_arch_initcall(centaur_init_cpu);
 
-int __init centaur_exit_cpu(void)
+static int __init centaur_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_CENTAUR] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/cyrix.c.old	2006-02-03 16:15:00.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/cyrix.c	2006-02-03 16:15:21.000000000 +0100
@@ -444,7 +444,7 @@
 
 //early_arch_initcall(cyrix_init_cpu);
 
-int __init cyrix_exit_cpu(void)
+static int __init cyrix_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_CYRIX] = NULL;
 	return 0;
@@ -467,7 +467,7 @@
 
 //early_arch_initcall(nsc_init_cpu);
 
-int __init nsc_exit_cpu(void)
+static int __init nsc_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_NSC] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/nexgen.c.old	2006-02-03 16:15:38.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/nexgen.c	2006-02-03 16:15:44.000000000 +0100
@@ -62,7 +62,7 @@
 
 //early_arch_initcall(nexgen_init_cpu);
 
-int __init nexgen_exit_cpu(void)
+static int __init nexgen_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_NEXGEN] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/rise.c.old	2006-02-03 16:15:57.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/rise.c	2006-02-03 16:16:27.000000000 +0100
@@ -52,7 +52,7 @@
 
 //early_arch_initcall(rise_init_cpu);
 
-int __init rise_exit_cpu(void)
+static int __init rise_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_RISE] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/transmeta.c.old	2006-02-03 16:16:37.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/transmeta.c	2006-02-03 16:16:50.000000000 +0100
@@ -112,7 +112,7 @@
 
 //early_arch_initcall(transmeta_init_cpu);
 
-int __init transmeta_exit_cpu(void)
+static int __init transmeta_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_TRANSMETA] = NULL;
 	return 0;
--- linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/umc.c.old	2006-02-03 16:17:02.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/arch/i386/kernel/cpu/umc.c	2006-02-03 16:17:12.000000000 +0100
@@ -32,7 +32,7 @@
 
 //early_arch_initcall(umc_init_cpu);
 
-int __init umc_exit_cpu(void)
+static int __init umc_exit_cpu(void)
 {
 	cpu_devs[X86_VENDOR_UMC] = NULL;
 	return 0;


  parent reply	other threads:[~2006-02-03 21:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  8:07 2.6.16-rc1-mm5 Andrew Morton
2006-02-03 10:17 ` 2.6.16-rc1-mm5 Benoit Boissinot
2006-02-03 20:13   ` 2.6.16-rc1-mm5 Benoit Boissinot
2006-02-03 20:36     ` 2.6.16-rc1-mm5 Andrew Morton
2006-02-03 11:51 ` [-mm patch] Makefile: remove a tab from an empty line Adrian Bunk
2006-02-03 20:57 ` [-mm patch] kernel/time/timeofday.c: make struct ts_interval static Adrian Bunk
2006-02-03 21:50   ` john stultz
2006-02-03 20:59 ` [-mm patch] kernel/timer.c: make some variables static Adrian Bunk
2006-02-03 21:02 ` [-mm patch] net/ipv4/fib_rules.c: make struct fib_rules static again Adrian Bunk
2006-02-04 23:51   ` David S. Miller
2006-02-03 21:09 ` [-mm patch] make some "struct clocksource" static Adrian Bunk
2006-02-03 21:12 ` Adrian Bunk [this message]
2006-02-03 21:25 ` 2.6.16-rc1-mm5: drivers/ieee1394/oui O=... builds broken Adrian Bunk
2006-02-04  2:43   ` Jody McIntyre
2006-02-04  9:20     ` Sam Ravnborg
2006-02-04  9:08   ` Stefan Richter
2006-02-04  9:30     ` Stefan Richter
2006-02-04  9:31     ` Johannes Berg
2006-02-04  9:58       ` Stefan Richter
2006-02-06  4:31   ` Jody McIntyre
2006-02-04  7:59 ` 2.6.16-rc1-mm5 Matthias Urlichs
2006-02-04  9:29 ` 2.6.16-rc1-mm5 Sam Ravnborg
2006-02-04  9:36   ` 2.6.16-rc1-mm5 Andrew Morton

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=20060203211227.GO4408@stusta.de \
    --to=bunk@stusta.de \
    --cc=76306.1226@compuserve.com \
    --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