From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 1/1] drivers: cpuidle: cpuidle-arm: heterogeneous systems extension
Date: Tue, 14 Jul 2015 11:04:51 +0100 [thread overview]
Message-ID: <20150714100451.GA16165@red-moon> (raw)
In-Reply-To: <CAGS+omBtraNBH43qsFn_YgO3ePbFav9VtwgqDUinbOBMPwOGXA@mail.gmail.com>
Hi Daniel,
On Tue, Jul 14, 2015 at 05:52:48AM +0100, Daniel Kurtz wrote:
[...]
> > Any further comments ? I can post a v2 with an updated idle_states_cmp()
> > return value, if we think the multiple drivers approach is valid.
>
> Can you post v2?
> From the silence on the list, I guess there is no strong objection to
> your approach.
I just wanted to make sure this patch is strictly required before asking
for a merge in the mainline, it adds to the code complexity so it should
not be taken lightly.
> So, perhaps it is time to remove the "RFC" as well so this can get on
> track to be merged.
I will drop the RFC status and add a simple configuration to define
a config entry to configure the max number of drivers statically so
that we do not waste memory for nothing.
Thanks,
Lorenzo
next prev parent reply other threads:[~2015-07-14 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 16:10 [RFC PATCH v2 0/1] ARM: cpuidle: heterogeneous systems extension Lorenzo Pieralisi
2015-04-16 16:10 ` [RFC PATCH v2 1/1] drivers: cpuidle: cpuidle-arm: " Lorenzo Pieralisi
2015-05-04 13:19 ` Daniel Lezcano
2015-05-05 15:56 ` Lorenzo Pieralisi
2015-05-12 13:03 ` Lorenzo Pieralisi
2015-07-14 4:52 ` Daniel Kurtz
2015-07-14 10:04 ` Lorenzo Pieralisi [this message]
2015-07-14 10:23 ` Lorenzo Pieralisi
2015-04-21 18:24 ` [RFC PATCH v2 0/1] ARM: cpuidle: " Kevin Hilman
2015-04-22 8:55 ` Lorenzo Pieralisi
2015-05-12 16:36 ` Lina Iyer
2015-04-30 15:51 ` Lorenzo Pieralisi
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=20150714100451.GA16165@red-moon \
--to=lorenzo.pieralisi@arm.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