[OpenPower-Firmware] [PATCH 0/9] Backport powernv-cpufreq bugfixes to openpower-linux

[Joel Stanley]

Hello Shilpa,

On Tue, Apr 12, 2016 at 4:33 PM, Shilpasri G Bhat
<shilpa.bhat at linux.vnet.ibm.com> wrote:
> Hi,
>
> Please apply this patch series to op-build linux tree to fix the bug
> where console is flushed with cpu frequency throttle messages.

Thanks for the patches.

Now that we have the openpower-firmware at lists.ozlabs.org mailing list,
we can use that to collect patches destined for the skiroot kernel.

I notice that most (all?) of the patches went upstream in the 4.5
merge window. That's good! However, none of them are cc'd to stable.
Everyone has their opinions on what stable means, but if they're
fixing a bug that users are seeing, then I think that qualifies.

If you cc your bugfixes to stable then they will be included in the
op-build firmware "automaticlly" when I update our kernels. Also, they
are more likely to be included in updates to distro kernels.

I'll add the above points to the HOWTO at
https://github.com/open-power/op-build/wiki/KernelTree. Sorry that I
had neglected this documentation; you did a great job following the
instructions.

However, see blow:

> Michael Neuling (1):
>   cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
>
> Shilpasri G Bhat (7):
>   cpufreq: powernv: Free 'chips' on module exit
>   cpufreq: powernv: Hot-plug safe the kworker thread
>   cpufreq: powernv: Remove cpu_to_chip_id() from hot-path
>   cpufreq: powernv/tracing: Add powernv_throttle tracepoint
>   cpufreq: powernv: Replace pr_info with trace print for throttle event
>   cpufreq: powernv: Fix bugs in powernv_cpufreq_{init/exit}
>   cpufreq: powernv: Add sysfs attributes to show throttle stats
>
> Viresh Kumar (1):
>   Revert "cpufreq: postfix policy directory with the first CPU in
>     related_cpus"

This is a long list of patches. Do we really need them all to fix the
issue described in the bugzilla?

> BZ : 139982

Until IBM has a bug tracker that members of the community can visit,
those bugzilla bug numbers are useless. Please describe the issue in
full when you post the patches.

Cheers,

Joel