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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 19 Sep 2017 15:36:45 -0700 From: Viresh Kumar <viresh.kumar@...aro.org> To: Dave Gerlach <d-gerlach@...com> Cc: sunil.m@...hveda.org, rjw@...ysocki.net, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, karthik@...hveda.org Subject: Re: [PATCH v2] drivers: cpufreq: Fix sysfs duplicate filename creation for platform-device On 19-09-17, 10:12, Dave Gerlach wrote: > Hi, > On 09/18/2017 02:18 PM, sunil.m@...hveda.org wrote: > > From: Suniel Mahesh <sunil.m@...hveda.org> > > > > ti-cpufreq and cpufreq-dt-platdev drivers are registering platform-device > > with same name "cpufreq-dt" using platform_device_register_*() routines. > > This is leading to build warnings appended below. > > > > Providing hardware information to OPP framework along with the platform- > > device creation should be done by ti-cpufreq driver before cpufreq-dt > > driver comes into place. > > > > This patch add's TI SoC am33xx (uses opp-v2 property) in the blacklist of > > devices in cpufreq-dt-platform driver to avoid creating platform-device > > twice and remove build warnings (suggested by Viresh Kumar). > > This looks good to me, but this also affects "ti,am43" and "ti,dra7" platforms, > care to add those to the blacklist as well with this patch? Thanks. Also please rebase on top of the pm/linux-next branch as I have pushed a similar patch there. (Actually its applied to pm/bleeding-edge branch for now and may take a day to get to pm/linux-next. You can wait in that case.). -- viresh
Powered by blists - more mailing lists