All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Cc: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Interrupt routing problem
Date: Thu, 15 Jan 2004 11:41:08 +0100	[thread overview]
Message-ID: <1074163267.1143.2.camel@localhost> (raw)
In-Reply-To: <20040113090003.GB3599-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>

Am Di, den 13.01.2004 schrieb Karol Kozimor um 10:00:
> Thus wrote Yu, Luming:
> > > (I believe
> > > there was a patch I tested and found working).
> > What patch ?
> I believe it was the one attached below -- my bookmarks went wild some time
> ago and I can't tell the bugzilla no., but it's certainly there.

[acpi_hw_enable_ec_gpes() patch]
I have tested this with 2.4.24 and at least it does no harm ;)
Since I do not know enough to judge if it is really necessary at least
from my point of view I would suggest to add it to the general ACPI
code.

> Best regards,
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  parent reply	other threads:[~2004-01-15 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  8:50 Interrupt routing problem Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CC3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13  9:00   ` Karol Kozimor
     [not found]     ` <20040113090003.GB3599-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-15 10:41       ` Nils Faerber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  4:14 Yu, Luming
2004-01-13  9:08 Yu, Luming
2004-01-12  5:28 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CA9-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13  8:26   ` Karol Kozimor
2004-01-07  8:50 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C83-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07  9:05   ` Karol Kozimor
     [not found]     ` <20040107090531.GA32086-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-07 15:34       ` Karol Kozimor
2004-01-05  2:17 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C75-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-06  4:10   ` Len Brown
     [not found]     ` <1073362251.2419.21.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-06  8:47       ` Karol Kozimor
2004-01-04 16:43 Nils Faerber

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=1074163267.1143.2.camel@localhost \
    --to=nils.faerber-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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.