From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] cpufreq: Avoid attempts to create duplicate symbolic links
Date: Wed, 29 Jul 2015 19:51:48 +0530 [thread overview]
Message-ID: <20150729142148.GF5100@linux> (raw)
In-Reply-To: <CAJZ5v0iUn0rSVSqyXscCfGgujpM7r9o9xjQgDOk+JQ=y6seRgQ@mail.gmail.com>
On 29-07-15, 15:57, Rafael J. Wysocki wrote:
> In practice, this means a cpufreq driver registration done in parallel
> with CPU hotplug.
Not necessarily. Also consider the case where cpufreq driver is already working
for a set of CPUs. And a new set of CPUs (that will share the policy) are
getting physically added to the system.
Anyway, even if there is no problem at all, I do agree with Russell that it will
be better to do operations on behalf of the devices only when we are requested
for those devices.
--
viresh
next prev parent reply other threads:[~2015-07-29 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 21:14 [PATCH] cpufreq: Avoid attempts to create duplicate symbolic links Rafael J. Wysocki
2015-07-24 14:09 ` Viresh Kumar
2015-07-24 20:20 ` Rafael J. Wysocki
2015-07-24 22:17 ` [PATCH v2] " Rafael J. Wysocki
2015-07-25 13:00 ` Viresh Kumar
2015-07-25 22:46 ` Rafael J. Wysocki
2015-07-26 0:28 ` [PATCH v3] " Rafael J. Wysocki
2015-07-27 2:29 ` Viresh Kumar
2015-07-27 12:39 ` Rafael J. Wysocki
2015-07-27 2:27 ` [PATCH v2] " Viresh Kumar
2015-07-27 13:45 ` Rafael J. Wysocki
2015-07-27 14:39 ` Viresh Kumar
2015-07-29 1:38 ` Rafael J. Wysocki
2015-07-29 5:45 ` Viresh Kumar
2015-07-29 9:11 ` Russell King - ARM Linux
2015-07-29 13:57 ` Rafael J. Wysocki
2015-07-29 14:21 ` Viresh Kumar [this message]
2015-07-29 20:32 ` Rafael J. Wysocki
2015-07-30 9:00 ` Viresh Kumar
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=20150729142148.GF5100@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rafael@kernel.org \
--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).