From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3: cpuidle: Add description field to each C-state.
Date: Thu, 03 Mar 2011 17:41:19 -0800 [thread overview]
Message-ID: <1299202879.3989.499.camel@vence> (raw)
In-Reply-To: <1297437132-1005-2-git-send-email-santosh.shilimkar@ti.com>
On Fri, 2011-02-11 at 20:42 +0530, Santosh Shilimkar wrote:
> Add a description field to each idle C-state. This helps to give
> better data with PowerTop and one don't have to refer to the code
> to link what Cx means from system point of view while analysing
> PowerTop data.
>
> No functional change.
>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
Looks good, queuing for 2.6.39 (branch: for_2.6.39/pm-misc)
Kevin
next prev parent reply other threads:[~2011-03-04 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 15:12 [PATCH] omap3: pm: Use exported set_cr() instead of a custom one Santosh Shilimkar
2011-02-11 15:12 ` [PATCH] omap3: cpuidle: Add description field to each C-state Santosh Shilimkar
2011-02-11 17:07 ` Jarkko Nikula
2011-02-12 7:42 ` Santosh Shilimkar
2011-03-04 1:41 ` Kevin Hilman [this message]
2011-02-15 0:08 ` [PATCH] omap3: pm: Use exported set_cr() instead of a custom one Kevin Hilman
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=1299202879.3989.499.camel@vence \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.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