From: Nick Piggin <piggin@cyberone.com.au>
To: Chris Wright <chrisw@osdl.org>, len.brown@intel.com
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net,
adq_dvb@lidskialf.net
Subject: Re: [PATCH] ACPI pci irq routing fix
Date: Sat, 27 Sep 2003 15:54:33 +1000 [thread overview]
Message-ID: <3F752619.5000406@cyberone.com.au> (raw)
In-Reply-To: <20030926182128.C24360@osdlab.pdx.osdl.net>
Chris Wright wrote:
>If irq.active is set from _CRS, make sure to use it, rather than trying
>anything from the from the _PRS list, as some machines don't handle this
>properly. This patch is against current linux-acpi-test-2.6.0. It's
>been floating about for a while, and fixes bug #1186.
>
>Patch originally from Andrew de Quincey.
>
>thanks,
>-chris
>
This fixes my bug #1257.
next prev parent reply other threads:[~2003-09-27 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-27 1:21 [PATCH] ACPI pci irq routing fix Chris Wright
2003-09-27 5:54 ` Nick Piggin [this message]
2003-09-30 5:17 ` Len Brown
2003-09-30 6:08 ` Chris Wright
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=3F752619.5000406@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=acpi-devel@lists.sourceforge.net \
--cc=adq_dvb@lidskialf.net \
--cc=chrisw@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@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