From: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Matthew Tippett
<matthew.tippett-rieW9WUcm8FFJ04o6PK0Fg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Possible ACPI IRQ Routing Bug
Date: Fri, 29 Apr 2005 17:26:50 +0800 [thread overview]
Message-ID: <20050429092650.GA4435@linux.sh.intel.com> (raw)
In-Reply-To: <427056E5.6040100-rieW9WUcm8FFJ04o6PK0Fg@public.gmane.org>
Care to describe the problem in details?
On 2005.04.27 23:22:13 -0400, Matthew Tippett wrote:
> Hi,
>
> I was wondering if I could find out who a domain expert is for
> understanding behaviours of ACPI + APIC + PIC.
>
> I am getting a full problem description created, but want to make sure I
> have the right audience first.
>
> Regards,
>
> Matthew
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
prev parent reply other threads:[~2005-04-29 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 3:22 Possible ACPI IRQ Routing Bug Matthew Tippett
[not found] ` <427056E5.6040100-rieW9WUcm8FFJ04o6PK0Fg@public.gmane.org>
2005-04-29 9:26 ` Yu, Luming [this message]
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=20050429092650.GA4435@linux.sh.intel.com \
--to=luming.yu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=matthew.tippett-rieW9WUcm8FFJ04o6PK0Fg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.