[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20140422112913.GB21613@lee--X1>
Date: Tue, 22 Apr 2014 12:29:13 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Stratos Karafotis <stratosk@...aphore.gr>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linus Walleij <linus.walleij@...aro.org>,
" linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry
macro for iteration
> > > 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@...aphore.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?
>
> I'm sorry for the confusion.
> I sent v3 only for patches 1/8 and 3/8.
> So, I was asked by Rafael to resend the entire series as v4
> in order to be clear which is the latest version in each patch.
> Unfortunately, I omit the change log :(
>
> The specific patch (5/8) is unchanged since v2.
>
> I'm sorry for the inconvenience.
That's okay, thanks for clarifying.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists