Messages in this thread | | | Subject | Re: [PATCH] cpufreq: Fix policy initialization for internal governor drivers | From | Artem Bityutskiy <> | Date | Thu, 27 Feb 2020 10:28:44 +0200 |
| |
On Wed, 2020-02-26 at 22:39 +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com> > > Before commit 1e4f63aecb53 ("cpufreq: Avoid creating excessively > large stack frames") the initial value of the policy field in struct > cpufreq_policy set by the driver's ->init() callback was implicitly > passed from cpufreq_init_policy() to cpufreq_set_policy() if the > default governor was neither "performance" nor "powersave". After > that commit, however, cpufreq_init_policy() must take that case into > consideration explicitly and handle it as appropriate, so make that > happen. > > Fixes: 1e4f63aecb53 ("cpufreq: Avoid creating excessively large stack frames") > Link: https://lore.kernel.org/linux-pm/39fb762880c27da110086741315ca8b111d781cd.camel@gmail.com/ > Reported-by: Artem Bityutskiy <dedekind1@gmail.com> > Cc: 5.4+ <stable@vger.kernel.org> # 5.4+ > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Many thanks, fixes the issue.
Artem.
| |