From: Len Brown <len.brown@intel.com>
To: linux-ia64@vger.kernel.org
Subject: IA64 allnoconfig buildfix
Date: Thu, 25 Aug 2005 14:57:03 +0000 [thread overview]
Message-ID: <1124982076.16880.8.camel@toshiba> (raw)
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Tony,
The ia64 allnoconfig build fails for some ACPI vs PCI reasons I've fixed
in my tree, but this small IA64 specific fix is needed also.
It stems from allnoconfig choosing CONFIG_PROC_FS=n
and sn_forc_interrupt_flag being defined within
CONFIG_PROC_FS, but used outside it.
cheers,
-Len
Index: linux-acpi-2.6/arch/ia64/sn/kernel/irq.c
===================================================================
--- linux-acpi-2.6.orig/arch/ia64/sn/kernel/irq.c
+++ linux-acpi-2.6/arch/ia64/sn/kernel/irq.c
@@ -23,7 +23,7 @@ static void force_interrupt(int irq);
static void register_intr_pda(struct sn_irq_info *sn_irq_info);
static void unregister_intr_pda(struct sn_irq_info *sn_irq_info);
-extern int sn_force_interrupt_flag;
+int sn_force_interrupt_flag = 1;
extern int sn_ioif_inited;
static struct list_head **sn_irq_lh;
static spinlock_t sn_irq_info_lock = SPIN_LOCK_UNLOCKED; /* non-IRQ
lock */
Index: linux-acpi-2.6/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
===================================================================
--- linux-acpi-2.6.orig/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
+++ linux-acpi-2.6/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
@@ -52,7 +52,7 @@ static int licenseID_open(struct inode *
* the bridge chip. The hardware will then send an interrupt message
if the
* interrupt line is active. This mimics a level sensitive interrupt.
*/
-int sn_force_interrupt_flag = 1;
+extern int sn_force_interrupt_flag;
static int sn_force_interrupt_show(struct seq_file *s, void *p)
{
[-- Attachment #2: SN-vs-CONFIG_PROC_FS=n.patch --]
[-- Type: text/x-patch, Size: 1214 bytes --]
Index: linux-acpi-2.6/arch/ia64/sn/kernel/irq.c
===================================================================
--- linux-acpi-2.6.orig/arch/ia64/sn/kernel/irq.c
+++ linux-acpi-2.6/arch/ia64/sn/kernel/irq.c
@@ -23,7 +23,7 @@ static void force_interrupt(int irq);
static void register_intr_pda(struct sn_irq_info *sn_irq_info);
static void unregister_intr_pda(struct sn_irq_info *sn_irq_info);
-extern int sn_force_interrupt_flag;
+int sn_force_interrupt_flag = 1;
extern int sn_ioif_inited;
static struct list_head **sn_irq_lh;
static spinlock_t sn_irq_info_lock = SPIN_LOCK_UNLOCKED; /* non-IRQ lock */
Index: linux-acpi-2.6/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
===================================================================
--- linux-acpi-2.6.orig/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
+++ linux-acpi-2.6/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
@@ -52,7 +52,7 @@ static int licenseID_open(struct inode *
* the bridge chip. The hardware will then send an interrupt message if the
* interrupt line is active. This mimics a level sensitive interrupt.
*/
-int sn_force_interrupt_flag = 1;
+extern int sn_force_interrupt_flag;
static int sn_force_interrupt_show(struct seq_file *s, void *p)
{
reply other threads:[~2005-08-25 14:57 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=1124982076.16880.8.camel@toshiba \
--to=len.brown@intel.com \
--cc=linux-ia64@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