| 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: <CAKohpontQwTc4KP7XMvtkvS2sQTyF+ngXnXfbJ1ev+MLEp-H0g@mail.gmail.com> Date: Fri, 20 Dec 2013 16:03:47 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: bilhuang <bilhuang@...dia.com> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>, Stephen Warren <swarren@...dotorg.org>, Thierry Reding <thierry.reding@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>, "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org> Subject: Re: [PATCH v5 1/1] cpufreq: tegra: Re-model Tegra20 cpufreq driver On 20 December 2013 15:55, bilhuang <bilhuang@...dia.com> wrote: > Don't you think it worth creating a file here so this can be shared to > arm64? We will see how to handle virtual devices when we will start getting arm64 SoCs. Probably we might end up writing a single file in cpufreq, if required, that will create virtual devices for every arm64 platform.. So, some people might use it and others wouldn't.. But no platform specific files for such stuff. So, the best we can do for now is to move these to platform code as we are talking about arm32 SoC's for now which do have a mach-* directory.. -- 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