From: Kevin Hilman <khilman@ti.com>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: venki@google.com, ak@linux.intel.com, len.brown@intel.com,
peterz@infradead.org, santosh.shilimkar@ti.com,
arjan@linux.intel.com, lenb@kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics
Date: Thu, 22 Sep 2011 19:45:32 +0000 [thread overview]
Message-ID: <87ty84tl7n.fsf@ti.com> (raw)
In-Reply-To: <20110922082840.10520.85895.stgit@localhost6.localdomain6> (Deepthi Dharwar's message of "Thu, 22 Sep 2011 13:58:52 +0530")
Deepthi Dharwar <deepthi@linux.vnet.ibm.com> writes:
> The following patch series implements global registration of cpuidle
> states, and also has the necessary data structure changes to
> accommodate the per-cpu writable members of the cpuidle_states
> structure.
I reviewed earlier versions of the series, and this version still looks
good to me. Any reason it is still RFC?
Reviewed-by: Kevin Hilman <khilman@ti.com>
and for the OMAP-specific parts,
Acked-by: Kevin Hilman <khilman@ti.com>
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@ti.com>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: venki@google.com, ak@linux.intel.com, len.brown@intel.com,
peterz@infradead.org, santosh.shilimkar@ti.com,
arjan@linux.intel.com, lenb@kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics
Date: Thu, 22 Sep 2011 12:45:32 -0700 [thread overview]
Message-ID: <87ty84tl7n.fsf@ti.com> (raw)
In-Reply-To: <20110922082840.10520.85895.stgit@localhost6.localdomain6> (Deepthi Dharwar's message of "Thu, 22 Sep 2011 13:58:52 +0530")
Deepthi Dharwar <deepthi@linux.vnet.ibm.com> writes:
> The following patch series implements global registration of cpuidle
> states, and also has the necessary data structure changes to
> accommodate the per-cpu writable members of the cpuidle_states
> structure.
I reviewed earlier versions of the series, and this version still looks
good to me. Any reason it is still RFC?
Reviewed-by: Kevin Hilman <khilman@ti.com>
and for the OMAP-specific parts,
Acked-by: Kevin Hilman <khilman@ti.com>
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics
Date: Thu, 22 Sep 2011 12:45:32 -0700 [thread overview]
Message-ID: <87ty84tl7n.fsf@ti.com> (raw)
In-Reply-To: <20110922082840.10520.85895.stgit@localhost6.localdomain6> (Deepthi Dharwar's message of "Thu, 22 Sep 2011 13:58:52 +0530")
Deepthi Dharwar <deepthi@linux.vnet.ibm.com> writes:
> The following patch series implements global registration of cpuidle
> states, and also has the necessary data structure changes to
> accommodate the per-cpu writable members of the cpuidle_states
> structure.
I reviewed earlier versions of the series, and this version still looks
good to me. Any reason it is still RFC?
Reviewed-by: Kevin Hilman <khilman@ti.com>
and for the OMAP-specific parts,
Acked-by: Kevin Hilman <khilman@ti.com>
Kevin
next prev parent reply other threads:[~2011-09-22 19:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 8:28 [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Deepthi Dharwar
2011-09-22 8:40 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with Deepthi Dharwar
2011-09-22 8:28 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Deepthi Dharwar
2011-09-22 8:30 ` [RFC PATCH V6 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Deepthi Dharwar
2011-09-22 8:42 ` [RFC PATCH V6 1/4] cpuidle: Move dev->last_residency update to driver Deepthi Dharwar
2011-09-22 8:30 ` [RFC PATCH V6 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Deepthi Dharwar
2011-09-22 8:31 ` [RFC PATCH V6 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Deepthi Dharwar
2011-09-22 8:43 ` [RFC PATCH V6 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and Deepthi Dharwar
2011-09-22 8:31 ` [RFC PATCH V6 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Deepthi Dharwar
2011-09-22 8:32 ` [RFC PATCH V6 3/4] cpuidle: Split cpuidle_state structure and move per-cpu statistics fields Deepthi Dharwar
2011-09-22 8:44 ` [RFC PATCH V6 3/4] cpuidle: Split cpuidle_state structure and move Deepthi Dharwar
2011-09-22 8:32 ` [RFC PATCH V6 3/4] cpuidle: Split cpuidle_state structure and move per-cpu statistics fields Deepthi Dharwar
2011-09-22 8:34 ` [RFC PATCH V6 4/4] cpuidle: Single/Global registration of idle states Deepthi Dharwar
2011-09-22 8:46 ` Deepthi Dharwar
2011-09-22 8:34 ` Deepthi Dharwar
2011-09-22 17:35 ` [RFC PATCH V6 0/4] cpuidle: Global " Arjan van de Ven
2011-09-22 17:35 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Arjan van de Ven
2011-09-22 17:35 ` Arjan van de Ven
2011-09-22 19:37 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states Jean Pihet
2011-09-22 19:37 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Jean Pihet
2011-09-22 19:37 ` Jean Pihet
2011-09-22 19:37 ` Jean Pihet
2011-09-22 19:45 ` Kevin Hilman [this message]
2011-09-22 19:45 ` Kevin Hilman
2011-09-22 19:45 ` Kevin Hilman
2011-09-23 11:07 ` Deepthi Dharwar
2011-09-23 11:19 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states Deepthi Dharwar
2011-09-23 11:07 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Deepthi Dharwar
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=87ty84tl7n.fsf@ti.com \
--to=khilman@ti.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=santosh.shilimkar@ti.com \
--cc=venki@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.