public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stratos Karafotis <stratosk@semaphore.gr>,
	Linus Walleij <linus.walleij@linaro.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v2 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
Date: Wed, 16 Apr 2014 15:03:51 +0100	[thread overview]
Message-ID: <20140416140351.GE19671@lee--X1> (raw)
In-Reply-To: <CAKohpongiw9kZJDBsnp4U5obzX_W-sWHX3GoKd3STtQmsw6GcA@mail.gmail.com>

> >> The cpufreq core now supports the cpufreq_for_each_entry macro helper
> >> for iteration over the cpufreq_frequency_table, so use it.
> >>
> >> It should have no functional changes.
> >>
> >> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
> >> ---
> >>  drivers/mfd/db8500-prcmu.c | 19 ++++++++-----------
> >>  1 file changed, 8 insertions(+), 11 deletions(-)
> >
> > Applied untested by me.
> 
> Wouldn't build. Let it go via Rafael.

Rafael, would you mind creating a branch from this patch set that we
can both pull from please?

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 22:26 [PATCH v2 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration Stratos Karafotis
2014-04-16 10:51 ` Lee Jones
2014-04-16 13:35   ` Viresh Kumar
2014-04-16 14:03     ` Lee Jones [this message]
2014-04-21 23:01 ` [PATCH v4 " Stratos Karafotis
2014-04-22  7:15   ` Lee Jones
2014-04-22 10:18     ` Rafael J. Wysocki
2014-04-22 11:27       ` Lee Jones
2014-04-22 11:49         ` Rafael J. Wysocki
2014-04-30 23:06           ` 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=20140416140351.GE19671@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sameo@linux.intel.com \
    --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