From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 Resend 0/2] CPUFreq Cleanup Part IV
Date: Wed, 30 Oct 2013 22:53:51 +0100 [thread overview]
Message-ID: <3389791.QB3z2L4pXG@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1383052613.git.viresh.kumar@linaro.org>
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
next prev parent reply other threads:[~2013-10-30 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 13:26 Viresh Kumar
2013-10-29 13:26 ` [PATCH V2 Resend 1/2] cpufreq: distinguish drivers that do asynchronous notifications Viresh Kumar
2013-10-29 13:26 ` [PATCH V2 Resend 2/2] cpufreq: move freq change notifications to cpufreq core Viresh Kumar
2013-10-30 21:53 ` Rafael J. Wysocki [this message]
2013-10-30 22:27 ` [PATCH V2 Resend 0/2] CPUFreq Cleanup Part IV Viresh Kumar
2013-10-30 23:07 ` Rafael J. Wysocki
2013-10-30 22:56 ` Viresh Kumar
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=3389791.QB3z2L4pXG@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®