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
| ||
|
Message-ID: <2299822.iEchLYNLbS@vostro.rjw.lan> Date: Thu, 15 Oct 2015 23:35:13 +0200 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Saravana Kannan <skannan@...eaurora.org> Cc: Viresh Kumar <viresh.kumar@...aro.org>, linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH V2 4/5] cpufreq: create cpu/cpufreq/policyX directories On Thursday, October 15, 2015 12:25:27 PM Saravana Kannan wrote: > On 10/15/2015 09:05 AM, Viresh Kumar wrote: > > The cpufreq sysfs interface had been a bit inconsistent as one of the > > CPUs for a policy had a real directory within its sysfs 'cpuX' directory > > and all other CPUs had links to it. That also made the code a bit > > complex as we need to take care of moving the sysfs directory if the CPU > > containing the real directory is getting physically hot-unplugged. > > > > Solve this by creating 'policyX' directories (per-policy) in > > /sys/devices/system/cpu/cpufreq/ directory, where X is the CPU for which > > the policy was first created. > > > > This also removes the need of keeping kobj_cpu and we can remove it now. > > > > Suggested-by: Saravana Kannan <skannan@...eaurora.org> > > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org> > > > Since you've added a separate patch for making policyX more consistent: > Reviewed-by: Saravana Kannan <skannan@...eaurora.org> > > Btw, does a Review-by have an implicit Acked-by? Yes it does, at least as far as I'm concerned. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists