From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 06/10] arch_topology: Use CPUFREQ_CREATE_POLICY instead of CPUFREQ_NOTIFY
Date: Thu, 25 Jul 2019 15:36:34 +0200 [thread overview]
Message-ID: <20190725133634.GA11115@kroah.com> (raw)
In-Reply-To: <3afc5046ba9435d229a004c17b005197488006d4.1563862014.git.viresh.kumar@linaro.org>
On Tue, Jul 23, 2019 at 11:44:06AM +0530, Viresh Kumar wrote:
> CPUFREQ_NOTIFY is going to get removed soon, lets use
> CPUFREQ_CREATE_POLICY instead of that here. CPUFREQ_CREATE_POLICY is
> called only once (which is exactly what we want here) for each cpufreq
> policy when it is first created.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> drivers/base/arch_topology.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-07-25 13:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:14 [PATCH V2 00/10] cpufreq: Migrate users of policy notifiers to QoS requests Viresh Kumar
2019-07-23 6:26 ` Viresh Kumar
2019-07-23 6:14 ` Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 01/10] cpufreq: Add policy create/remove notifiers Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 02/10] thermal: cpu_cooling: Switch to QoS requests instead of cpufreq notifier Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 03/10] powerpc: macintosh: " Viresh Kumar
2019-07-23 6:14 ` Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 04/10] cpufreq: powerpc_cbe: " Viresh Kumar
2019-08-09 2:34 ` Viresh Kumar
2019-08-09 9:01 ` Rafael J. Wysocki
2019-08-19 2:26 ` Viresh Kumar
2019-08-19 6:42 ` Rafael J. Wysocki
2019-08-19 6:47 ` Viresh Kumar
2019-08-10 12:19 ` Rafael J. Wysocki
2019-07-23 6:14 ` [PATCH V2 05/10] ACPI: cpufreq: " Viresh Kumar
2019-08-05 9:42 ` [Devel] " Rafael J. Wysocki
2019-08-05 9:42 ` Rafael J. Wysocki
2019-08-06 4:39 ` Viresh Kumar
2019-08-06 8:01 ` [Devel] " Rafael J. Wysocki
2019-08-06 8:01 ` Rafael J. Wysocki
2019-08-06 8:47 ` Viresh Kumar
2019-08-09 2:33 ` Viresh Kumar
2019-08-28 8:50 ` [PATCH V3 " Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 06/10] arch_topology: Use CPUFREQ_CREATE_POLICY instead of CPUFREQ_NOTIFY Viresh Kumar
2019-07-25 13:36 ` Greg Kroah-Hartman [this message]
2019-07-23 6:14 ` [PATCH V2 07/10] video: sa1100fb: Remove cpufreq policy notifier Viresh Kumar
2019-07-23 6:26 ` Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 08/10] video: pxafb: " Viresh Kumar
2019-07-23 6:26 ` Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 09/10] cpufreq: Remove CPUFREQ_ADJUST and CPUFREQ_NOTIFY policy notifier events Viresh Kumar
2019-07-23 6:14 ` [PATCH V2 10/10] Documentation: cpufreq: Update policy notifier documentation Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2019-08-10 12:13 [Devel] [PATCH V2 05/10] ACPI: cpufreq: Switch to QoS requests instead of cpufreq notifier Rafael J. Wysocki
2019-08-10 12:13 ` Rafael J. Wysocki
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=20190725133634.GA11115@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--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.