Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 2 Feb 2021 10:25:11 +0530 you wrote:
> During cpufreq driver's registration, if the ->init() callback for all
> the CPUs fail then there is not much point in keeping the driver around
> as it will only account for more of unnecessary noise, for example
> cpufreq core will try to suspend/resume the driver which never got
> registered properly.
>
> The removal of such a driver is avoided if the driver carries the
> CPUFREQ_STICKY flag. This was added way back [1] in 2004 and perhaps no
> one should ever need it now. A lot of drivers do set this flag, probably
> because they just copied it from other drivers.
>
> [...]
Here is the summary with links:
- [V2] cpufreq: Remove CPUFREQ_STICKY flag
https://git.kernel.org/qcom/c/5ae4a4b45d43
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
