From: Stas Sergeev <stsp-D1TkPCJej5s@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
Linux kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Re: Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2)
Date: Thu, 02 Dec 2004 19:52:12 +0300 [thread overview]
Message-ID: <41AF483C.5040909@aknet.ru> (raw)
In-Reply-To: <1101879708.8028.62.camel@d845pe>
Hello.
Len Brown wrote:
> Please confirm that this patch make the problem go away in the
Confirmed, thanks!
(Andrew, sorry for failing to reply to
you query, and now you know the latest
status anyway. I'll start posting the
-rc2-mm4 problems soon.)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-02 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41990138.7080008@aknet.ru>
[not found] ` <41990138.7080008-D1TkPCJej5s@public.gmane.org>
2004-11-23 6:09 ` Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Len Brown
2004-11-24 18:12 ` Stas Sergeev
[not found] ` <41A4CF1C.6090503-D1TkPCJej5s@public.gmane.org>
2004-11-24 22:44 ` Len Brown
2004-11-25 18:18 ` Stas Sergeev
[not found] ` <41A621DD.8060102-D1TkPCJej5s@public.gmane.org>
2004-12-01 5:41 ` Len Brown
2004-12-01 5:44 ` Len Brown
2004-12-02 16:52 ` Stas Sergeev [this message]
2004-11-26 0:53 Li, Shaohua
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=41AF483C.5040909@aknet.ru \
--to=stsp-d1tkpcjej5s@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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