linux-kernel - Re: [PATCH] Revert "cpufreq: postfix policy directory with the first CPU in related

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Mar 2016 16:39:27 +0700
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Rafael Wysocki <rjw@...ysocki.net>
Cc:	linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org,
	skannan@...eaurora.org, shilpa.bhat@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "cpufreq: postfix policy directory with the first
 CPU in related_cpus"

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).
-- 
viresh