From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] don't assume iosapic interrupt controllers
Date: Wed, 03 Mar 2004 19:03:26 +0000 [thread overview]
Message-ID: <16454.11262.62539.919876@napali.hpl.hp.com> (raw)
In-Reply-To: <20040301224526.GA22182@sgi.com>
>>>>> On Wed, 3 Mar 2004 09:28:35 -0800, jbarnes@sgi.com (Jesse Barnes) said:
Jesse> Some ia64 machines don't use an iosapic interrupt controller
Jesse> (a flagrant violation of the DIG64 spec, gasp!), so don't
Jesse> assume it's there in mca.c. This patch got no complaints
Jesse> last time I posted it, so I'm proposing it for inclusion.
Your changelog explains why you want to remove the offending code. It
doesn't explain why the change is safe for those machines that do have
I/O SAPIC. Please provide a complete ChangeLog entry (along with the
patch).
Thanks,
--david
next prev parent reply other threads:[~2004-03-03 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 22:45 [PATCH] don't assume iosapic interrupt controller in mca.c Jesse Barnes
2004-03-03 17:28 ` [PATCH] don't assume iosapic interrupt controllers Jesse Barnes
2004-03-03 19:03 ` David Mosberger [this message]
2004-03-03 19:22 ` [PATCH] don't assume iosapic interrupt controllers take 2 Jesse Barnes
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=16454.11262.62539.919876@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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