[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160609032100.GB9356@vireshk-i7>
Date: Thu, 9 Jun 2016 08:51:00 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Linux PM list <linux-pm@...r.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: governor: Drop gov_cancel_work()
On 09-06-16, 01:45, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>
> There's no reason for gov_cancel_work() to exist at all, as it only
> has one caller and the only thing done by that caller is to invoke
> gov_cancel_work().
>
> Accordingly, drop gov_cancel_work() and move its contents to the
> caller.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> ---
> drivers/cpufreq/cpufreq_governor.c | 19 +++++++------------
> 1 file changed, 7 insertions(+), 12 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
I am wondering what happened to your other patches around the governor callbacks
and why weren't they applied yet :)
--
viresh
Powered by blists - more mailing lists