[RESEND] cpuidle for ARM pull request

On Wednesday, October 16, 2013 06:35:24 PM Daniel Lezcano wrote:

On 07/27/2013 02:37 PM, Rafael J. Wysocki wrote:

quoted

On Saturday, July 27, 2013 08:13:31 AM Daniel Lezcano wrote:

quoted

On 07/26/2013 02:07 AM, Rafael J. Wysocki wrote:

quoted

On Friday, July 26, 2013 12:41:09 AM Rafael J. Wysocki wrote:

quoted

On Friday, July 26, 2013 12:29:08 AM Rafael J. Wysocki wrote:

quoted

On Friday, July 26, 2013 12:07:03 AM Daniel Lezcano wrote:

quoted

On 07/16/2013 02:04 PM, Daniel Lezcano wrote:

quoted

[ ... ]

quoted

Next time, can you please add a general description of what the patches do and
why they do that to the pull request?

quoted

I thought it would have been easier for us if I could based my PRs on
top of your linux-next branch, so acting as a proxy for ARM patches. I
am maintaining the clocksource drivers and I am basing my tree on top of
tip/core.

I guess you are rebasing your tree often and this is an issue for you,
right ?

Yes, my linux-next branch may contain commits that will be modified later
(e.g. ACKs added, fixes folded in etc.).

Anyway, as I said, as long as the material you have for me doesn't depend on
anything new in my tree, it's better to base it on top of an -rc kernel.

In case it does depend on that, I've put the entire outstanding cpuidle
material into my pm-cpuidle branch (including your ARM commits just pulled).

Hi Rafael,

is it possible to update the pm-cpuidle branch ? so I can base my pull 
request on it. There will be a (trivial) conflict in the Makefile and 
Kconfig.arm if I base my PR on v3.12-rc5.

Updated, but you can base it on 3.12-rc5 if you need to.

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.