From: Jes Sorensen <jes-UC6nUKlm/0l5V+5IkYBVeNBPR1lH4CV8@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: akpm-3NddpPZAyC0@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Jesse Barnes <jbarnes-sJ/iWh9BUns@public.gmane.org>
Subject: Re: [patch] 2.6.1-mm3 acpi frees free irq0
Date: 15 Jan 2004 17:01:51 -0500 [thread overview]
Message-ID: <yq0d69k27n4.fsf@wildopensource.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC89CC-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
>>>>> "Len" == Brown, Len <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:
Len> The primary failure is that the SCI was not found, and the
Len> secondary symptom is that we failed to handle that error properly
Len> -- which you've patched.
Len> Can you tell me more about the primary failure? Was the SCI
Len> found in other releases?
Hi Len,
In this specific case the prom doesn't have it in it's tables, so not
finding it is expected behavior.
Cheers,
Jes
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-15 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 17:19 [patch] 2.6.1-mm3 acpi frees free irq0 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC89CC-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-01-15 22:01 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 6:29 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CEE-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-19 7:59 ` Jes Sorensen
2004-01-15 14:56 Jes Sorensen
[not found] ` <16390.43574.867869.286685-4mDQ13Tdud8Jw5R7aSpS0dP8p4LwMBBS@public.gmane.org>
2004-01-15 15:11 ` Martin Lorenz
2004-01-26 20:30 ` Len Brown
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=yq0d69k27n4.fsf@wildopensource.com \
--to=jes-uc6nuklm/0l5v+5ikybvenbpr1lh4cv8@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=jbarnes-sJ/iWh9BUns@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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