From: Kevin Radloff <radsaq-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Fw: Followup on 2.6.13-rc3 ACPI processor C-state regression
Date: Thu, 14 Jul 2005 07:32:01 -0400 [thread overview]
Message-ID: <3b0ffc1f05071404326a9e0e94@mail.gmail.com> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD3057502AA9A8C-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 7/13/05, Li, Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> There is a patch from Jindrich which should fix your issue. See
> http://sourceforge.net/mailarchive/forum.php?thread_id=7640723&forum_id=
> 6102
>
> Thanks,
> Shaohua
Thanks. I actually ended up testing the same code and it does indeed
fix the problem.
--
Kevin 'radsaq' Radloff
radsaq-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
http://saqataq.us/
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
next prev parent reply other threads:[~2005-07-14 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 3:00 Fw: Followup on 2.6.13-rc3 ACPI processor C-state regression Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD3057502AA9A8C-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-14 11:32 ` Kevin Radloff [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 23:13 Andrew Morton
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=3b0ffc1f05071404326a9e0e94@mail.gmail.com \
--to=radsaq-re5jqeeqqe8avxtiumwx3w@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=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