Kernel warning in cpufreq_add_dev()

Kernel warning in cpufreq_add_dev() · linux@armlinux.org.uk (Russell King - ARM Linux) · 2016-08-19
Kernel warning in cpufreq_add_dev() · Rafael J. Wysocki <hidden> · 2016-08-20
Kernel warning in cpufreq_add_dev() · viresh.kumar@linaro.org (Viresh Kumar) · 2016-08-20
Kernel warning in cpufreq_add_dev() · Rafael J. Wysocki <hidden> · 2016-08-22
Kernel warning in cpufreq_add_dev() · viresh.kumar@linaro.org (Viresh Kumar) · 2016-08-24
Kernel warning in cpufreq_add_dev() · Rafael J. Wysocki <hidden> · 2016-08-31
Kernel warning in cpufreq_add_dev() · viresh.kumar@linaro.org (Viresh Kumar) · 2016-08-31
Kernel warning in cpufreq_add_dev() · rafael@kernel.org (Rafael J. Wysocki) · 2016-08-31
Kernel warning in cpufreq_add_dev() · viresh.kumar@linaro.org (Viresh Kumar) · 2016-09-09
[PATCH] cpufreq: create link to policy only for registered CPUs · Viresh Kumar <viresh.kumar@linaro.org> · 2016-09-09
Re: [PATCH] cpufreq: create link to policy only for registered CPUs · Russell King - ARM Linux <linux@armlinux.org.uk> · 2016-09-09
Re: [PATCH] cpufreq: create link to policy only for registered CPUs · Viresh Kumar <viresh.kumar@linaro.org> · 2016-09-09
Re: [PATCH] cpufreq: create link to policy only for registered CPUs · Russell King - ARM Linux <linux@armlinux.org.uk> · 2016-09-09
Re: [PATCH] cpufreq: create link to policy only for registered CPUs · Viresh Kumar <viresh.kumar@linaro.org> · 2016-09-09
Re: [PATCH] cpufreq: create link to policy only for registered CPUs · Russell King - ARM Linux <linux@armlinux.org.uk> · 2016-09-09
[PATCH V2] cpufreq: create link to policy only for registered CPUs · Viresh Kumar <viresh.kumar@linaro.org> · 2016-09-12
Re: [PATCH V2] cpufreq: create link to policy only for registered CPUs · Rafael J. Wysocki <hidden> · 2016-09-14

From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2016-09-09 09:57:42
Also in: linux-pm

On 31-08-16, 03:26, Rafael J. Wysocki wrote:

I was thinking about something similar, but won't the WARN_ON()s in
cpufreq_add/remove_dev_symlink() still trigger, say if there's more
than one CPU in a policy and both happen to be online initially?

Right. I missed that. I have sent a patch just now in reply to the first email
from Russell. That should fix it all..

@Russell: Can you please test/verify the patch I have sent now?

-- 
viresh

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help