public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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, linux@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13
Date: Tue, 13 Aug 2013 22:01:17 +0200	[thread overview]
Message-ID: <1437762.edDpfxPldn@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1376392060.git.viresh.kumar@linaro.org>

On Tuesday, August 13, 2013 07:01:04 PM Viresh Kumar wrote:
> Hi Rafael/Russell,
> 
> These patches would be part of this patchset finally, sending it separately as I
> didn't wanted to send other patches in that series..
> 
> https://lkml.org/lkml/2013/8/10/48
> 
> (Above series was rebased over https://lkml.org/lkml/2013/8/8/263 and hence this
> patchset too)..
> 
> These first exposes frequency table and then uses cpufreq generic routines
> (which uses exposed table) instead of its own .verify() routine.
> 
> Later I will send another patch that would be part of this series:
> 
> http://lkml.org/lkml/2013/8/12/406
> 
> (I need to send that series again today and so not sending that patch twice,
> once here and then in that series)..
> 
> All these patches are pushed here with all dependencies:
> 
> https://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-v3.13

Are the three patches in this series prerequisite for the big target_index
one?  If so, I think they can go into 3.12 actually, if they are ACKed by the
appropriate platform maintainers.

> Viresh Kumar (3):
>   cpufreq: sa11x0: Expose frequency table
>   cpufreq: sa11x0: let cpufreq core initialize struct policy fields
>   cpufreq: sa11x0: Use generic cpufreq routines
> 
>  arch/arm/mach-sa1100/generic.c   | 65 +++++++++++++---------------------------
>  arch/arm/mach-sa1100/generic.h   |  2 +-
>  drivers/cpufreq/sa1100-cpufreq.c |  9 +++---
>  drivers/cpufreq/sa1110-cpufreq.c |  9 +++---
>  4 files changed, 30 insertions(+), 55 deletions(-)

Thanks,
Rafael


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

  parent reply	other threads:[~2013-08-13 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 13:31 [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13 Viresh Kumar
2013-08-13 13:31 ` [PATCH 1/3] cpufreq: sa11x0: Expose frequency table Viresh Kumar
2013-08-13 13:31 ` [PATCH 2/3] cpufreq: sa11x0: let cpufreq core initialize struct policy fields Viresh Kumar
2013-08-13 13:31 ` [PATCH 3/3] cpufreq: sa11x0: Use generic cpufreq routines Viresh Kumar
2013-08-13 20:01 ` Rafael J. Wysocki [this message]
2013-08-14  2:26   ` [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13 Viresh Kumar
2013-08-14 13:14     ` Rafael J. Wysocki

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=1437762.edDpfxPldn@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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