From: Lee Jones <lee.jones@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stratos Karafotis <stratosk@semaphore.gr>,
Linus Walleij <linus.walleij@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v4 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
Date: Tue, 22 Apr 2014 12:27:17 +0100 [thread overview]
Message-ID: <20140422112717.GA21613@lee--X1> (raw)
In-Reply-To: <6612075.PRZcWcuj98@vostro.rjw.lan>
On Tue, 22 Apr 2014, Rafael J. Wysocki wrote:
> On Tuesday, April 22, 2014 08:15:41 AM Lee Jones wrote:
> > > 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>
> > > ---
> >
> > It would be good to have a changelog which describes the differences
> > between the versions, so we can keep track.
> >
> > > drivers/mfd/db8500-prcmu.c | 19 ++++++++-----------
> > > 1 file changed, 8 insertions(+), 11 deletions(-)
> >
> > So it looks like I already applied v2 of this patch to my tree. What
> > changed in v3 and v4? Should I remove that patch from MFD and apply
> > this one instead?
>
> The reason why v4 was sent is because I asked for it.
>
> And if you applied [5/8] without [1/8], it won't work, because the macro is
> introduced by that patch.
That's right, which is why I mailed you about it:
> > > 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?
> If that's the case, please drop [5/8] and let me handle the entire series.
I'm happy for you to apply the series and send me a pull-request for
either a) the entire series or b) just the patches which touch MFD and
any subsequent decencies. Or I can apply them and send you one.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-04-22 11:27 UTC|newest]
Thread overview: 11+ 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
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 [this message]
2014-04-22 11:49 ` Rafael J. Wysocki
2014-04-30 23:06 ` Rafael J. Wysocki
[not found] <535635d0.8908b40a.6c36.ffffaaa9SMTPIN_ADDED_MISSING@mx.google.com>
2014-04-22 11:29 ` Lee Jones
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=20140422112717.GA21613@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=linux-pm@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