[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gh41=19yHaZFRyxNd7uiVcU8sxhMpiZS64y+RYGYzBnA@mail.gmail.com>
Date: Wed, 9 Mar 2016 14:12:19 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Saravana Kannan <skannan@...eaurora.org>,
Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert "cpufreq: postfix policy directory with the first
CPU in related_cpus"
On Wed, Mar 9, 2016 at 10:39 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> On 03-03-16, 14:51, Viresh Kumar wrote:
>> This reverts commit 3510fac45492 ("cpufreq: postfix policy directory
>> with the first CPU in related_cpus").
>>
>> Earlier, the policy->kobj was added to the kobject core, before ->init()
>> callback was called for the cpufreq drivers. Which allowed those drivers
>> to add or remove, driver dependent, sysfs files/directories to the same
>> kobj from their ->init() and ->exit() callbacks.
>>
>> That isn't possible anymore after commit 3510fac45492 got applied.
>>
>> Now, there is no other clean alternative that people can adopt.
>>
>> Its better to revert the earlier commit to allow cpufreq drivers to
>> create/remove sysfs files from ->init() and ->exit() callbacks.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
>
> Sorry about missing SoB (Just noticed it in bleeding-edge).
For a revert that's not a problem, but I'll add it.
Thanks,
Rafael
Powered by blists - more mailing lists