From: Eric Valette <eric.valette@free.fr>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: "Brown, Len" <len.brown@intel.com>,
Jeff Garzik <jgarzik@pobox.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
"J.A. Magallon" <jamagallon@able.es>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
acpi-devel@sourceforge.net
Subject: Re: [ACPI] RE: [patch] 2.4.x ACPI updates
Date: Sun, 24 Aug 2003 12:36:33 +0200 [thread overview]
Message-ID: <3F489531.6040408@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.55L.0308231826470.5824@freak.distro.conectiva>
Marcelo Tosatti wrote:
>
> On Sat, 23 Aug 2003, Brown, Len wrote:
>
>
>>>>Len,
>>>>
>>>>Patch applied, thanks.
>>
>>Great!
>>
>>
>>>>Do you have any further information on the ACPI oops
>>>
>>>reports I sent you?
>>
>>
>>I see this one in my inbox "Subject: 2.4.22-xx powerdown oddities" and
>>will follow-up.
>>
>>If there are more, then forward them to me directly -- the mailing lists
>>have had some really weird latencies lately.
>
>
> plus this one
>
> ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106146576326309&w=2
Note that i have the same computer on run 2.4 ACPI for months without
problems...
-- eric
next prev parent reply other threads:[~2003-08-24 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 21:05 [patch] 2.4.x ACPI updates Brown, Len
2003-08-23 21:30 ` Marcelo Tosatti
2003-08-23 22:33 ` [ACPI] " Karol Kozimor
2003-09-02 14:37 ` Pavel Machek
2003-09-08 13:29 ` Karol Kozimor
2003-09-09 7:32 ` Karol Kozimor
2003-08-24 10:36 ` Eric Valette [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 23:55 Brown, Len
2003-08-20 0:04 Brown, Len
2003-08-20 18:15 ` Marcelo Tosatti
2003-08-20 23:06 ` [ACPI] " Sérgio Monteiro Basto
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=3F489531.6040408@free.fr \
--to=eric.valette@free.fr \
--cc=acpi-devel@sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--cc=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).