All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH V2 0/2] cpufreq: cpufreq-dt: Improvements for set_target()
Date: Fri, 24 Oct 2014 09:21:04 +0200	[thread overview]
Message-ID: <5449FDE0.9020101@i2se.com> (raw)
In-Reply-To: <CAKohpokjczrGvZ6e7JOwkPtq1-MC0Cr_s+bp=wwKt4x+FdumWQ@mail.gmail.com>

Am 20.10.2014 um 06:43 schrieb Viresh Kumar:
> On 18 October 2014 03:39, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>> This patch series contains 2 improvements for set_target().
>>
>> changes in V2:
>>   - rebase because of name change cpufreq-cpu0 to cpufreq-dt
>>
>> Stefan Wahren (2):
>>   cpufreq: cpufreq-dt: Improve debug about matching OPP
>>   cpufreq: cpufreq-dt: Handle regulator_get_voltage() failure
>>
>>  drivers/cpufreq/cpufreq-dt.c |    9 +++++++--
>>  1 file changed, 7 insertions(+), 2 deletions(-)
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

Thanks. But maybe the patch series won't apply anymore.

Should i rebase again?

Stefan


  reply	other threads:[~2014-10-24  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 22:09 [PATCH V2 0/2] cpufreq: cpufreq-dt: Improvements for set_target() Stefan Wahren
2014-10-17 22:09 ` [PATCH V2 1/2] cpufreq: cpufreq-dt: Improve debug about matching OPP Stefan Wahren
2014-10-17 22:09 ` [PATCH V2 2/2] cpufreq: cpufreq-dt: Handle regulator_get_voltage() failure Stefan Wahren
2014-10-20  4:43 ` [PATCH V2 0/2] cpufreq: cpufreq-dt: Improvements for set_target() Viresh Kumar
2014-10-24  7:21   ` Stefan Wahren [this message]
2014-11-08  1:40     ` Rafael J. Wysocki
2014-11-08  8:01       ` Stefan Wahren

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=5449FDE0.9020101@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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.