cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	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>
Subject: Re: [PATCH v2 0/8] Introduce new cpufreq helper macros
Date: Wed, 16 Apr 2014 09:31:34 +0530	[thread overview]
Message-ID: <CAKohpomvmpiYkQAP7Yb=TNxNsXMVh1_MLuK7KQrdEkf15MyvMg@mail.gmail.com> (raw)
In-Reply-To: <534DB1CC.60407@semaphore.gr>

On 16 April 2014 03:55, Stratos Karafotis <stratosk@semaphore.gr> wrote:
> Hi all,
>
> 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.
>
> Changes v1 -> v2
>         - Rearrange patches
>         - Remove redundant braces
>         - Fix a newly introduced bug in exynos5440
>         - Use cpufreq_for_each_valid_entry instead of
> cpufreq_for_each_entry in cpufreq_frequency_table_get_index()
>         - Drop redundant double ! operator in longhaul and change

You dropped this !! in thermal stuff and not longhaul :)

> the pos loop cursor variable to freq_pos.
>         - Declare pos variable on a separate line
>
> Stratos Karafotis (8):
>   cpufreq: Introduce macros for cpufreq_frequency_table iteration
>   cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
>   davinci: da850: Use cpufreq_for_each_entry macro for iteration
>   mips: lemote 2f: se cpufreq_for_each_entry macro for iteration
>   mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
>   thermal: cpu_cooling: Use cpufreq_for_each_valid_entry macro for
>     iteration
>   irda: sh_sir: Use cpufreq_for_each_valid_entry macro for iteration
>   sh: clk: Use cpufreq_for_each_valid_entry macro for iteration

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

  reply	other threads:[~2014-04-16  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 22:25 [PATCH v2 0/8] Introduce new cpufreq helper macros Stratos Karafotis
2014-04-16  4:01 ` Viresh Kumar [this message]
2014-04-16  7:04   ` Stratos Karafotis

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='CAKohpomvmpiYkQAP7Yb=TNxNsXMVh1_MLuK7KQrdEkf15MyvMg@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dirk.j.brandewie@intel.com \
    --cc=egtvedt@samfundet.no \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=stratosk@semaphore.gr \
    /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;
as well as URLs for NNTP newsgroup(s).