From: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-dev
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Dominik Brodowski <linux-JhLEnvuH02M@public.gmane.org>,
"Pallipadi,
Venkatesh"
<venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
Subject: RE: [PATCH]Modular C-state policy
Date: Wed, 12 Oct 2005 14:08:17 +0800 [thread overview]
Message-ID: <1129097298.3928.3.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3004D954F8-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, 2005-10-12 at 13:26 +0800, Brown, Len wrote:
> it would be helpful to have a prose summary
> that explains the benefits of this patch
> so that reviewers can make sense of the diff.
This patch actually hasn't any benefit. It just makes it easier to add
new C-state policy. Its C-sate algorithm is the same with current. The
purpose is to make C-state policy smoothly move to new one.
Thanks,
Shaohua
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
next prev parent reply other threads:[~2005-10-12 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 5:26 [PATCH]Modular C-state policy Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3004D954F8-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-10-12 6:08 ` Shaohua Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 2:14 Shaohua Li
[not found] ` <1129083270.4159.10.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-10-22 19:29 ` Dominik Brodowski
[not found] ` <20051022192940.GB7082-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-10-24 2:05 ` Shaohua Li
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=1129097298.3928.3.camel@linux-hp.sh.intel.com \
--to=shaohua.li-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-JhLEnvuH02M@public.gmane.org \
--cc=trenn-l3A5Bk7waGM@public.gmane.org \
--cc=venkatesh.pallipadi-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