From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Nick Piggin <piggin-/x7JMgtu12E0n/F98K4Iww@public.gmane.org>
Cc: Chris Wright <chrisw-3NddpPZAyC0@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Andrew de Quincey
<adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Subject: Re: [PATCH] ACPI pci irq routing fix
Date: 30 Sep 2003 01:17:22 -0400 [thread overview]
Message-ID: <1064899042.2532.101.camel@dhcppc4> (raw)
In-Reply-To: <3F752619.5000406-/x7JMgtu12E0n/F98K4Iww@public.gmane.org>
On Sat, 2003-09-27 at 01:54, Nick Piggin wrote:
> Chris Wright wrote:
>
> >If irq.active is set from _CRS, make sure to use it
...
> and fixes bug #1186.
> >
> >Patch originally from Andrew de Quincey.
> >
>
> This fixes my bug #1257.
>
This fix has been integrated with others in the ACPI patch,
and is available now in these bitkeeper trees:
http://linux-acpi.bkbits.net/linux-acpi-test-2.4.22
http://linux-acpi.bkbits.net/linux-acpi-test-2.4.23
http://linux-acpi.bkbits.net/linux-acpi-test-2.6.0
It is also available as a plain patch "acpi_pci_link_allocate" here:
ftp.kernel.org:/pub/linux/kernel/people/lenb/acpi/patches/test/*
thanks,
-Len
next prev parent reply other threads:[~2003-09-30 5:17 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
[not found] ` <20030926182128.C24360-BI/OLcgY7/cyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>
2003-09-27 5:54 ` Nick Piggin
[not found] ` <3F752619.5000406-/x7JMgtu12E0n/F98K4Iww@public.gmane.org>
2003-09-30 5:17 ` Len Brown [this message]
[not found] ` <1064899042.2532.101.camel-D2Zvc0uNKG8@public.gmane.org>
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=1064899042.2532.101.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org \
--cc=chrisw-3NddpPZAyC0@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piggin-/x7JMgtu12E0n/F98K4Iww@public.gmane.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