All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	" linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
Date: Tue, 22 Apr 2014 12:29:13 +0100	[thread overview]
Message-ID: <20140422112913.GB21613@lee--X1> (raw)
In-Reply-To: <535635d0.8908b40a.6c36.ffffaaa9SMTPIN_ADDED_MISSING@mx.google.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> 
> > > --- 
> >
> > 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

WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
Date: Tue, 22 Apr 2014 12:29:13 +0100	[thread overview]
Message-ID: <20140422112913.GB21613@lee--X1> (raw)
In-Reply-To: <535635d0.8908b40a.6c36.ffffaaa9SMTPIN_ADDED_MISSING@mx.google.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> 
> > > --- 
> >
> > 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

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <535635d0.8908b40a.6c36.ffffaaa9SMTPIN_ADDED_MISSING@mx.google.com>
2014-04-22 11:29 ` Lee Jones [this message]
2014-04-22 11:29   ` [PATCH v4 5/8] mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration Lee Jones
2014-04-15 22:26 [PATCH v2 " Stratos Karafotis
2014-04-21 23:01 ` [PATCH v4 " Stratos Karafotis
2014-04-21 23:01   ` Stratos Karafotis
2014-04-22  7:15   ` Lee Jones
2014-04-22  7:15     ` Lee Jones
2014-04-22 10:18     ` Rafael J. Wysocki
2014-04-22 10:18       ` Rafael J. Wysocki
2014-04-22 11:27       ` Lee Jones
2014-04-22 11:27         ` Lee Jones
2014-04-22 11:49         ` Rafael J. Wysocki
2014-04-22 11:49           ` Rafael J. Wysocki
2014-04-30 23:06           ` 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=20140422112913.GB21613@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.