From: Stephen Warren <swarren@wwwdotorg.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
rjw@rjwysocki.net, swarren@nvidia.com
Cc: linaro-kernel@lists.linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed
Date: Tue, 18 Feb 2014 13:05:59 -0700 [thread overview]
Message-ID: <5303BD27.4000905@wwwdotorg.org> (raw)
In-Reply-To: <324f43fc664f51eec355b08b6c2d4cedd2140b4c.1392628861.git.viresh.kumar@linaro.org>
On 02/17/2014 02:22 AM, Viresh Kumar wrote:
> Earlier patch tried to do this but missed this piece of code to fix.
>
> 42f921a cpufreq: remove sysfs files for CPUs which failed to come back after
> resume
>
> Currently we are getting this on suspend/resume:
>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 877 at fs/sysfs/dir.c:52 sysfs_warn_dup+0x68/0x84()
> sysfs: cannot create duplicate filename '/devices/system/cpu/cpu1/cpufreq'
...
> Fix this by removing sysfs link for cpufreq directory when cpu removed isn't
> policy->cpu.
Tested-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2014-02-18 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 9:22 [PATCH] cpufreq: remove sysfs link when a cpu != policy->cpu, is removed Viresh Kumar
2014-02-17 22:03 ` Rafael J. Wysocki
2014-04-07 17:15 ` Sören Brinkmann
2014-04-07 17:15 ` Sören Brinkmann
2014-04-07 17:15 ` Sören Brinkmann
2014-04-08 4:22 ` Viresh Kumar
2014-04-08 4:22 ` Viresh Kumar
2014-02-18 20:05 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-08 4:21 Viresh Kumar
2014-04-08 12:09 ` 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=5303BD27.4000905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=swarren@nvidia.com \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.