public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki•net>
To: Viresh Kumar <viresh.kumar@linaro•org>
Cc: linux-pm@vger•kernel.org,
	Vincent Guittot <vincent.guittot@linaro•org>,
	linux@dominikbrodowski•net,
	Benjamin Herrenschmidt <benh@kernel•crashing.org>,
	Ingo Molnar <mingo@redhat•com>, Jonathan Corbet <corbet@lwn•net>,
	Len Brown <lenb@kernel•org>,
	linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
	linuxppc-dev@lists•ozlabs.org,
	Michael Ellerman <mpe@ellerman•id.au>,
	Paul Mackerras <paulus@samba•org>,
	Peter Zijlstra <peterz@infradead•org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux•intel.com>,
	Sudeep Holla <sudeep.holla@arm•com>
Subject: Re: [PATCH V3 0/9] cpufreq: transition-latency cleanups
Date: Wed, 19 Jul 2017 14:42:02 +0200	[thread overview]
Message-ID: <2155547.8AYfQSCbsT@aspire.rjw.lan> (raw)
In-Reply-To: <cover.1500373914.git.viresh.kumar@linaro.org>

On Wednesday, July 19, 2017 03:42:40 PM Viresh Kumar wrote:
> Hi Rafael,
> 
> This series tries to cleanup the code around transition-latency and its
> users. Some of the old legacy code, which may not make much sense now,
> is dropped as well. And some code consolidation is also done across
> governors.
> 
> Based of: v4.13-rc1
> Tested on: ARM64 Hikey board.

>From the first quick look this version is fine by me.

Unless I find anything of concern later, this will be queued up for 4.14.

Thanks,
Rafael

      parent reply	other threads:[~2017-07-19 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:12 [PATCH V3 0/9] cpufreq: transition-latency cleanups Viresh Kumar
2017-07-19 10:12 ` [PATCH V3 8/9] cpufreq: Add CPUFREQ_NO_AUTO_DYNAMIC_SWITCHING cpufreq driver flag Viresh Kumar
2017-07-19 16:30   ` Dominik Brodowski
2017-07-19 12:42 ` Rafael J. Wysocki [this message]

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=2155547.8AYfQSCbsT@aspire.rjw.lan \
    --to=rjw@rjwysocki$(echo .)net \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=corbet@lwn$(echo .)net \
    --cc=lenb@kernel$(echo .)org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-pm@vger$(echo .)kernel.org \
    --cc=linux@dominikbrodowski$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mingo@redhat$(echo .)com \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=paulus@samba$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=srinivas.pandruvada@linux$(echo .)intel.com \
    --cc=sudeep.holla@arm$(echo .)com \
    --cc=vincent.guittot@linaro$(echo .)org \
    --cc=viresh.kumar@linaro$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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