public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: Compilation problem in arch/ia64/sn/kernel/setup.c
Date: Mon, 15 Mar 2004 16:59:39 +0000	[thread overview]
Message-ID: <20040315165939.GA1363@sgi.com> (raw)
In-Reply-To: <002b01c40a55$d5b392f0$39624c0f@india.hp.com>

The patch looks fine, but I wonder if we really need CONFIG_IA64_MCA
anymore, does anyone really want to run without it?

Jesse

On Mon, Mar 15, 2004 at 11:52:03AM +0530, Sourav Sen wrote:
> Hello,
> 
> In arch/ia64/sn/kernel/setup.c in 2.6.4 + IA64 patch,
> the array, platform_intr_list[] is declared
> as:
> 
> #ifdef CONFIG_IA64_MCA
> extern int platform_intr_list[];
> #endif
> 
> but is used without that (CONFIG_IA64_MCA) guard.
> So, I have done the following to get around the
> compilation problem. Somebody knowledgeable on
> this will be able to validate if this is the
> right way.
> 
> regards
> Sourav
> 
> --- arch/ia64/sn/kernel/setup.c.orig    Mon Mar 15 05:58:30 2004
> +++ arch/ia64/sn/kernel/setup.c Mon Mar 15 05:59:14 2004
> @@ -311,7 +311,9 @@
>         else
>                 sn_rtc_cycles_per_second = ticks_per_sec;
>  
> +#ifdef CONFIG_IA64_MCA
>         platform_intr_list[ACPI_INTERRUPT_CPEI] = IA64_CPE_VECTOR;
> +#endif
>  
>  
>         if ( IS_RUNNING_ON_SIMULATOR() )
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-03-15 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15  6:34 Compilation problem in arch/ia64/sn/kernel/setup.c Sourav Sen
2004-03-15 16:59 ` Jesse Barnes [this message]
2004-03-15 21:40 ` David Mosberger

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=20040315165939.GA1363@sgi.com \
    --to=jbarnes@sgi.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