ACK: [SRU][Artful][Bionic][PATCH 0/1] cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
Colin Ian King
colin.king at canonical.com
Mon Feb 26 11:13:01 UTC 2018
On 16/02/18 16:30, Joseph Salisbury wrote:
> BugLink: http://bugs.launchpad.net/bugs/1746174
> == SRU Justification ==
> Commit 09ca4c9b5958 introduced a bug in v4.8-rc2. The bug is that
> an error happens in CPU frequency reporting when nominal and min pstates
> are the same (cpufreq). Commit 3fa4680b8 fixes this issue.
> Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to upstream stable.
> == Fix ==
> commit 3fa4680b860bf48b437d6a2c039789c4abe202ae
> Author: Shilpasri G Bhat <shilpa.bhat at linux.vnet.ibm.com>
> Date: Fri Jan 12 12:43:53 2018 +0530
> cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
> == Regression Potential ==
> Low. This commit been cc'd to upstream stable, so it has had additional
> upstream review.
> == Test Case ==
> A test kernel was built with this patch and tested by the original bug reporter.
> The bug reporter states the test kernel resolved the bug.
> Shilpasri G Bhat (1):
> cpufreq: powernv: Dont assume distinct pstate values for nominal and
> drivers/cpufreq/powernv-cpufreq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Positive testing of an upstream commit, so looks fine to me,
Acked-by: Colin Ian King <colin.king at canonical.com>
More information about the kernel-team