From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Kernel warning in cpufreq_add_dev()
Date: Fri, 9 Sep 2016 15:27:42 +0530 [thread overview]
Message-ID: <20160909095742.GA18547@vireshk-i7> (raw)
In-Reply-To: <1496109.Jd9MGDryNS@vostro.rjw.lan>
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
next prev parent reply other threads:[~2016-09-09 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 11:00 Kernel warning in cpufreq_add_dev() Russell King - ARM Linux
2016-08-20 1:29 ` Rafael J. Wysocki
2016-08-20 1:46 ` Viresh Kumar
2016-08-22 17:32 ` Rafael J. Wysocki
2016-08-24 13:13 ` Viresh Kumar
2016-08-31 1:26 ` Rafael J. Wysocki
2016-08-31 4:11 ` Viresh Kumar
2016-08-31 11:58 ` Rafael J. Wysocki
2016-09-09 9:57 ` Viresh Kumar [this message]
2016-09-09 9:54 ` [PATCH] cpufreq: create link to policy only for registered CPUs Viresh Kumar
2016-09-09 11:16 ` Russell King - ARM Linux
2016-09-09 11:22 ` Viresh Kumar
2016-09-09 11:28 ` Russell King - ARM Linux
2016-09-09 11:34 ` Viresh Kumar
2016-09-09 12:53 ` Russell King - ARM Linux
2016-09-12 6:37 ` [PATCH V2] " Viresh Kumar
2016-09-14 1:00 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160909095742.GA18547@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).