From: David Mosberger <davidm@napali.hpl.hp.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
davidm@hpl.hp.com, Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
benjamin.liu@intel.com, iod00d@hp.com,
kaneshige.kenji@jp.fujitsu.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix PCI interrupt setting for ia64
Date: Mon, 08 Mar 2004 22:10:27 +0000 [thread overview]
Message-ID: <16460.61267.364413.100233@napali.hpl.hp.com> (raw)
In-Reply-To: <200403081505.21644.bjorn.helgaas@hp.com>
>>>>> On Mon, 8 Mar 2004 15:05:21 -0700, Bjorn Helgaas <bjorn.helgaas@hp.com> said:
Bjorn> My inclination is that it's better to help find ACPI bugs,
Bjorn> and if broken tables turn out to be a problem, we can add
Bjorn> some kind of command-line switch or blacklist to deal with
Bjorn> it. But I guess we should really get David's opinion, since
Bjorn> this is a potential issue for 2.6 distributions.
I agree with Bjorn's reasoning, but think that the patch should be
tested first on a Big Sur machine (with the latest official firmware).
If something breaks with old firmware, we can then at least ask the
affected people to upgrade their firmware (or come up with a kernel
workaround).
--david
next prev parent reply other threads:[~2004-03-08 22:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 2:49 [PATCH] fix PCI interrupt setting for ia64 Kenji Kaneshige
2004-03-08 6:30 ` Grant Grundler
2004-03-08 21:37 ` David Mosberger
2004-03-08 7:34 ` Liu, Benjamin
2004-03-08 7:44 ` Liu, Benjamin
2004-03-08 9:25 ` Takayoshi Kochi
2004-03-08 19:12 ` Bjorn Helgaas
2004-03-08 19:13 ` Bjorn Helgaas
2004-03-08 21:44 ` David Mosberger
2004-03-08 21:54 ` Russell King
2004-03-08 22:05 ` Bjorn Helgaas
2004-03-08 22:10 ` David Mosberger [this message]
2004-03-08 22:41 ` Bjorn Helgaas
2004-03-08 22:50 ` David Mosberger
2004-03-08 8:31 ` Kenji Kaneshige
2004-03-08 9:14 ` Liu, Benjamin
2004-03-08 10:42 ` Kenji Kaneshige
2004-03-08 10:46 ` Kenji Kaneshige
2004-03-10 20:09 ` David Mosberger
2004-03-11 0:34 ` Kenji Kaneshige
2004-03-11 1:34 ` Takayoshi Kochi
2004-03-11 7:22 ` David Mosberger
2004-03-11 5:29 ` Kenji Kaneshige
2004-03-11 7:33 ` 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=16460.61267.364413.100233@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=benjamin.liu@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=davidm@hpl.hp.com \
--cc=iod00d@hp.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=t-kochi@bq.jp.nec.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