mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	Hans-Christian Egtvedt <egtvedt@samfundet.no>,
	Dirk Brandewie <dirk.j.brandewie@intel.com>,
	linux-doc@vger.kernel.org,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Simon Horman <horms@verge.net.au>, Sekhar Nori <nsekhar@ti.com>,
	Samuel Ortiz <samuel@sortiz.org>
Subject: Re: [PATCH v5 0/8] Introduce new cpufreq helper macros
Date: Wed, 30 Apr 2014 00:26:07 +0200	[thread overview]
Message-ID: <1621123.rMC9JtD3Mo@vostro.rjw.lan> (raw)
In-Reply-To: <535FCDBD.6080500@semaphore.gr>

On Tuesday, April 29, 2014 07:05:17 PM Stratos Karafotis wrote:
> On 29/04/2014 07:17 πμ, Viresh Kumar wrote:
> > On 26 April 2014 01:45, Stratos Karafotis <stratosk@semaphore.gr> wrote:
> >> This patch set introduces two freq_table helper macros which
> >> can be used for iteration over cpufreq_frequency_table and
> >> makes the necessary changes to cpufreq core and drivers that
> >> use such an iteration procedure.
> >>
> >> The motivation was a usage of common procedure to iterate over
> >> cpufreq_frequency_table across all drivers and cpufreq core.
> >>
> >> This was tested on a x86_64 platform.
> >> Most files compiled successfully but unfortunately I was not
> >> able to compile sh_sir.c pasemi_cpufreq.c and ppc_cbe_cpufreq.c
> >> due to lack of cross compiler.
> >>
> >> Changelog
> >>
> >> v4 -> v5
> >>         - Fix warnings in printk format specifier for 32 bit
> >>           architectures in freq_table.c, longhaul, pasemi, ppc_cbe
> > 
> > Doesn't look much has changed and so it stays as is:
> > 
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > 
> 
> Thank you very much!

I've applied the series to my bleeding-edge branch, will move it to linux-next
after build testing later this week.

Thanks!

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

  reply	other threads:[~2014-04-29 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 20:15 Stratos Karafotis
2014-04-29  4:17 ` Viresh Kumar
2014-04-29 16:05   ` Stratos Karafotis
2014-04-29 22:26     ` Rafael J. Wysocki [this message]
2014-04-30 15:37       ` Stratos Karafotis
2014-05-06 15:24       ` Geert Uytterhoeven
2014-05-06 17:55         ` Stratos Karafotis
2014-05-07  5:23           ` Viresh Kumar
2014-05-07 13:13             ` Rafael J. Wysocki
2014-05-07 13:34               ` Stratos Karafotis
2014-05-07 13:36                 ` Viresh Kumar
2014-05-07 22:37                 ` 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=1621123.rMC9JtD3Mo@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=cpufreq@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dirk.j.brandewie@intel.com \
    --cc=egtvedt@samfundet.no \
    --cc=horms@verge.net.au \
    --cc=jesper.nilsson@axis.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=rdunlap@infradead.org \
    --cc=samuel@sortiz.org \
    --cc=stratosk@semaphore.gr \
    --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®