All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Chris Redpath <chris.redpath@arm.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3] cpufreq: schedutil: Examine the correct CPU when we update util
Date: Tue, 7 Nov 2017 11:09:00 +0100	[thread overview]
Message-ID: <CAJZ5v0g11-45dW_Hgw7wzE+wWbznM4Hcan77FjuP8__wSGC=pg@mail.gmail.com> (raw)
In-Reply-To: <20171107095951.GE3297@vireshk-i7>

On Tue, Nov 7, 2017 at 10:59 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 07-11-17, 09:49, Chris Redpath wrote:
>> Hi Viresh, Rafael,
>>
>> Without this patch, schedutil is totally broken for us - is
>> there any chance at all this could go in 4.14 or is it just
>> too late?
>
> I see that Rafael has already applied it, but not sure if he is planning to send
> it for 4.14 (though he should IMHO, as it is a critical fix).

Yes, I am.

Thanks,
Rafael

  reply	other threads:[~2017-11-07 10:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 10:54 [PATCH] cpufreq: schedutil: Examine the correct CPU when we update util Chris Redpath
2017-11-02 11:10 ` Viresh Kumar
2017-11-02 11:38   ` [PATCH v2] " Chris Redpath
2017-11-02 11:40     ` Viresh Kumar
2017-11-02 12:06       ` Chris Redpath
2017-11-03  3:40         ` Viresh Kumar
2017-11-03 13:36           ` [PATCH v3] " Chris Redpath
2017-11-03 15:45             ` Viresh Kumar
2017-11-07  9:49               ` Chris Redpath
2017-11-07  9:59                 ` Viresh Kumar
2017-11-07 10:09                   ` Rafael J. Wysocki [this message]
2017-11-07 11:03                     ` Chris Redpath

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='CAJZ5v0g11-45dW_Hgw7wzE+wWbznM4Hcan77FjuP8__wSGC=pg@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=chris.redpath@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.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.