From: Arjan van de Ven <arjan@linux.intel.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
Trinabh Gupta <g.trinabh@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
linux-tegra@vger.kernel.org, Colin Cross <ccross@android.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] cpuidle: allow per cpu latencies
Date: Thu, 05 Apr 2012 06:37:13 -0700 [thread overview]
Message-ID: <4F7DA009.4010802@linux.intel.com> (raw)
In-Reply-To: <1333619620-21201-1-git-send-email-pdeschrijver@nvidia.com>
On 4/5/2012 2:53 AM, Peter De Schrijver wrote:
> This patch doesn't update all cpuidle device registrations. I will do that
question is if you want to do per cpu latencies, or if you want to have
both types of C state in one big table, and have each of the tegra cpyu
types pick half of them...
next prev parent reply other threads:[~2012-04-05 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 9:53 [RFC PATCH] cpuidle: allow per cpu latencies Peter De Schrijver
2012-04-05 13:37 ` Arjan van de Ven [this message]
[not found] ` <4F7DA009.4010802-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2012-04-06 10:32 ` Shilimkar, Santosh
2012-04-06 15:35 ` Daniel Lezcano
[not found] ` <4F7F0D52.8080305-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-04-10 10:28 ` Peter De Schrijver
2012-04-16 15:34 ` Peter De Schrijver
2012-04-19 9:14 ` Daniel Lezcano
[not found] ` <4F8FD773.5030500-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-04-19 10:23 ` Peter De Schrijver
2012-04-10 10:31 ` Peter De Schrijver
-- strict thread matches above, loose matches on Subject: below --
2012-04-05 10:44 Peter De Schrijver
2012-04-05 11:25 Peter De Schrijver
2012-04-05 12:03 ` Peter 'p2' De Schrijver
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=4F7DA009.4010802@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=ccross@android.com \
--cc=daniel.lezcano@linaro.org \
--cc=deepthi@linux.vnet.ibm.com \
--cc=g.trinabh@gmail.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.com \
--cc=swarren@wwwdotorg.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