[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3389791.QB3z2L4pXG@vostro.rjw.lan>
Date: Wed, 30 Oct 2013 22:53:51 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: linaro-kernel@...ts.linaro.org, patches@...aro.org,
cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 Resend 0/2] CPUFreq Cleanup Part IV
On Tuesday, October 29, 2013 06:56:05 PM Viresh Kumar wrote:
> Hi Rafael,
>
> Thanks for applying all earlier patches for v3.13. There are only few left after
> this patchset, i.e. only set with these changes: "create cpufreq_generic_get()
> routine"..
>
> This patchset moves cpufreq-notifications to core and make ->target_index()
> routines really light weight and gets rid of a lot of redundant code.
>
> It is already reviewed/Acked/Tested by few people and so should be stable
> enough.
>
> See if you can still get these for 3.13..
>
> Viresh Kumar (2):
> cpufreq: distinguish drivers that do asynchronous notifications
> cpufreq: move freq change notifications to cpufreq core
[2/2] doesn't apply for me cleanly on top of the big/little changes.
Care to rebase on top of the new bleeding-edge I've just pushed?
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists