public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [ia64 R&D] CONFIG_IA64_MCA
Date: Tue, 04 May 2004 15:19:08 +0000	[thread overview]
Message-ID: <200405040819.08506.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <EFC4A8BDEDB4B846BC47F0ED773E812C0734C47C@xsun09.ptp.hp.com>

On Tuesday, May 4, 2004 6:53 am, Luck, Tony wrote:
> John> Hi, I have heard rumors that the CONFIG_IA64_MCA option may be
> John> phased out. If this is true, this email is an attempt to lobby
> John> AGAINST such a move.  I work with a team that explicitly
> John> disables the CONFIG_IA64_MCA so that the kernel will NOT
> John> handle MCAs. If kernel handling of MCAs is made automatic,
> John> then that would interfere with our use of the
> John> kernel. Hopefully, this rumor is false.
>
> Would a boot option to skip registration linux handlers with
> SAL work for you?  That would allow us to keep Jesse's cleanup
> that removes a bunch of #ifdefs.

That seems like an even better option, since it means they wouldn't have to 
recompile their kernel (unless they're making other changes), and may be 
useful in general.

Jesse

  parent reply	other threads:[~2004-05-04 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 18:35 FW: [ia64 R&D] CONFIG_IA64_MCA John Curry
2004-05-03 18:41 ` Jesse Barnes
2004-05-04 13:53 ` Luck, Tony
2004-05-04 15:19 ` Jesse Barnes [this message]
2004-05-04 16:06 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-04 16:34 ` Jesse Barnes
2004-05-05  2:51 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 19:57 ` Jesse Barnes
2004-05-07 21:19 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 21:28 ` Chen, Kenneth W
2004-05-07 21:32 ` Jesse Barnes
2004-08-03 13:57 ` Sourav Sen
2004-08-03 16:00 ` Jesse Barnes
2004-08-03 16:43 ` Luck, Tony

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