From: "Alex,Shi" <alex.shi@intel.com>
To: tony.luck@intel.com, tglx@linutronix.de,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Chen, Tim C" <tim.c.chen@intel.com>, "Shi, Alex" <alex.shi@intel.com>
Subject: [tip:ia64/urgent] Fix sn_force_interrupt_flag no defination issue
Date: Wed, 30 Mar 2011 11:01:29 +0800 [thread overview]
Message-ID: <1301454089.15889.170.camel@debian> (raw)
sn_force_interrupt_flag was removed in 39-rc1 patch. But it still be
used in arch/ia64/sn/kernel/sn2/sn_proc_fs.c. that make compilation
failed:
arch/ia64/sn/built-in.o: In function `sn_force_interrupt_show':
sn_proc_fs.c:(.text+0xd281): undefined reference to `sn_force_interrupt_flag'
sn_proc_fs.c:(.text+0xd2a0): undefined reference to `sn_force_interrupt_flag'
A quick fix for this.
Signed-off-by: Alex Shi <alex.shi@intel.com>
---
arch/ia64/sn/kernel/sn2/sn_proc_fs.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/ia64/sn/kernel/sn2/sn_proc_fs.c b/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
index c76d8dc..ce3215d 100644
--- a/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
+++ b/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
@@ -51,7 +51,7 @@ static int licenseID_open(struct inode *inode, struct file *file)
* the bridge chip. The hardware will then send an interrupt message if the
* interrupt line is active. This mimics a level sensitive interrupt.
*/
-extern int sn_force_interrupt_flag;
+int sn_force_interrupt_flag;
static int sn_force_interrupt_show(struct seq_file *s, void *p)
{
reply other threads:[~2011-03-30 2:59 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=1301454089.15889.170.camel@debian \
--to=alex.shi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.com \
--cc=tony.luck@intel.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