From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] cpufreq: governor: Get rid of governor events
Date: Mon, 16 May 2016 10:24:52 +0530 [thread overview]
Message-ID: <20160516045452.GO9296@vireshk-i7> (raw)
In-Reply-To: <2126576.ycyxhAHC04@vostro.rjw.lan>
On 14-05-16, 01:02, Rafael J. Wysocki wrote:
> --- linux-pm.orig/drivers/cpufreq/cpufreq_governor.c
> -int cpufreq_governor_dbs(struct cpufreq_policy *policy, unsigned int event)
> -{
> - if (event == CPUFREQ_GOV_POLICY_INIT) {
> - return cpufreq_governor_init(policy);
> - } else if (policy->governor_data) {
So, we aren't checking this anymore.
I am not sure (right now) if this will be a problem.
--
viresh
next prev parent reply other threads:[~2016-05-16 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 22:58 [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events Rafael J. Wysocki
2016-05-13 22:59 ` [PATCH 1/5] cpufreq: governor: CPUFREQ_GOV_LIMITS never fails Rafael J. Wysocki
2016-05-13 23:00 ` [PATCH 2/5] cpufreq: governor: Check transition latecy at init time only Rafael J. Wysocki
2016-05-13 23:01 ` [PATCH 3/5] cpufreq: governor: Simplify performance and powersave governors Rafael J. Wysocki
2016-05-13 23:01 ` [PATCH 4/5] cpufreq: Split cpufreq_governor() into simpler functions Rafael J. Wysocki
2016-05-13 23:02 ` [PATCH 5/5] cpufreq: governor: Get rid of governor events Rafael J. Wysocki
2016-05-16 4:54 ` Viresh Kumar [this message]
2016-05-16 4:55 ` [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events Viresh Kumar
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=20160516045452.GO9296@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox