From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Marcos D. Marado Torres"
<marado-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org>
Cc: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>,
Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [BKPATCH] ACPI for 2.6.10
Date: 05 Dec 2004 22:36:16 -0500 [thread overview]
Message-ID: <1102304175.2312.25.camel@d845pe> (raw)
In-Reply-To: <Pine.LNX.4.61.0412031840340.19044-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org>
On Fri, 2004-12-03 at 13:46, Marcos D. Marado Torres wrote:
> If this release is equivalent with -mm's bk-acpi.patch from
> 2.6.10-rc2-mm1 to 2.6.10-rc2-mm4,
> notice that this kernels' bk-acpi patches have the bug
> described in http://lkml.org/lkml/2004/11/16/263 , so I wouldn't
> really like to
> see this pull done to 2.6.10 until the problem is solved...
>
> If you want, I can try this patch to see if it acts like
> bk-acpi.patch, but I guess it does...
Please try 2.6.10-rc3, which includes this set of patches.
Yes, this set of patches includes most of what was in -mm, but not
everything. Note also, that it includes some more recent patches,
including a poweroff fix, that was not in the -mm patches above.
If your system still fails I'll be very interested to figure out exactly
what we did to make it stop working.
thanks,
-Len
-------------------------------------------------------
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-06 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 23:57 [BKPATCH] ACPI for 2.6.10 Len Brown
2004-12-03 18:46 ` Marcos D. Marado Torres
[not found] ` <Pine.LNX.4.61.0412031840340.19044-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org>
2004-12-06 3:36 ` Len Brown [this message]
2004-12-06 3:51 ` Marcos D. Marado Torres
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=1102304175.2312.25.camel@d845pe \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marado-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org \
--cc=torvalds-3NddpPZAyC0@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