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>
Cc: Hariprasad Nellitheertha <hari@in.ibm.com>, linux-kernel@vger.kernel.org
Subject: [-mm patch] i386 crash_dump: make a function static (fwd)
Date: Sat, 15 Jan 2005 22:40:08 +0100	[thread overview]
Message-ID: <20050115214008.GW4274@stusta.de> (raw)

The patch forwarded below still applies and compiles against 
2.6.11-rc1-mm1.

Please apply.


----- Forwarded message from Adrian Bunk <bunk@stusta.de> -----

Date:	Wed, 1 Dec 2004 22:39:39 +0100
From: Adrian Bunk <bunk@stusta.de>
To: Hariprasad Nellitheertha <hari@in.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] i386 crash_dump: make a function static

The patch below makes a needlessly global function static.


diffstat output:
 arch/i386/kernel/crash_dump.c |   13 ++++++-------
 include/asm-i386/crash_dump.h |    1 -
 2 files changed, 6 insertions(+), 8 deletions(-)


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

--- linux-2.6.10-rc2-mm4-full/include/asm-i386/crash_dump.h.old	2004-12-01 07:53:20.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/include/asm-i386/crash_dump.h	2004-12-01 07:53:26.000000000 +0100
@@ -13,7 +13,6 @@
 
 extern struct pt_regs crash_smp_regs[NR_CPUS];
 extern long crash_smp_current_task[NR_CPUS];
-extern void crash_dump_save_this_cpu(struct pt_regs *, int);
 extern void __crash_dump_stop_cpus(void);
 extern void crash_get_current_regs(struct pt_regs *regs);
 
--- linux-2.6.10-rc2-mm4-full/arch/i386/kernel/crash_dump.c.old	2004-12-01 07:53:36.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/arch/i386/kernel/crash_dump.c	2004-12-01 08:06:40.000000000 +0100
@@ -28,6 +28,12 @@
 extern void crash_dump_send_ipi(void);
 extern void stop_this_cpu(void *);
 
+static void crash_dump_save_this_cpu(struct pt_regs *regs, int cpu)
+{
+	crash_smp_current_task[cpu] = (long)current;
+	crash_smp_regs[cpu] = *regs;
+}
+
 static int crash_dump_nmi_callback(struct pt_regs *regs, int cpu)
 {
 	if (!crash_dump_expect_ipi[cpu])
@@ -96,10 +102,3 @@
 
 	regs->eip = (unsigned long)current_text_addr();
 }
-
-void crash_dump_save_this_cpu(struct pt_regs *regs, int cpu)
-{
-	crash_smp_current_task[cpu] = (long)current;
-	crash_smp_regs[cpu] = *regs;
-}
-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

----- End forwarded message -----


                 reply	other threads:[~2005-01-15 21:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050115214008.GW4274@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=hari@in.ibm.com \
    --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