From: Josh Triplett <josht@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: [-rt PATCH] i386: Mark nmi_show_regs static
Date: Fri, 20 Jul 2007 11:51:40 -0700 [thread overview]
Message-ID: <1184957501.2630.20.camel@josh-work.beaverton.ibm.com> (raw)
Nothing outside of arch/i386/kernel/nmi.c uses nmi_show_regs, so mark it
static.
Eliminates a sparse warning introduced in -rt:
warning: symbol 'nmi_show_regs' was not declared. Should it be static?
Signed-off-by: Josh Triplett <josh@kernel.org>
---
arch/i386/kernel/nmi.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/i386/kernel/nmi.c b/arch/i386/kernel/nmi.c
index 2a1e3c1..8155d1a 100644
--- a/arch/i386/kernel/nmi.c
+++ b/arch/i386/kernel/nmi.c
@@ -324,7 +324,7 @@ EXPORT_SYMBOL(touch_nmi_watchdog);
extern void die_nmi(struct pt_regs *, const char *msg);
-int nmi_show_regs[NR_CPUS];
+static int nmi_show_regs[NR_CPUS];
void nmi_show_all_regs(void)
{
--
1.5.2.1
reply other threads:[~2007-07-20 18:52 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=1184957501.2630.20.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).