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
| ||
|
Date: Mon, 5 Oct 2020 10:12:44 +0100 From: Jon Hunter <jonathanh@...dia.com> To: Viresh Kumar <viresh.kumar@...aro.org> CC: Sumit Gupta <sumitg@...dia.com>, <rjw@...ysocki.net>, <thierry.reding@...il.com>, <linux-pm@...r.kernel.org>, <linux-tegra@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <ksitaraman@...dia.com>, <bbasu@...dia.com> Subject: Re: [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq On 05/10/2020 05:34, Viresh Kumar wrote: > On 17-09-20, 09:36, Jon Hunter wrote: >> Viresh, ideally we need to include this fix for v5.9. Do you need Sumit >> to resend with the Fixes tag or are you happy to add? > > I understand that this fixes a patch which got merged recently, but I am not > sure if anything is broken badly right now, i.e. will make the hardware work > incorrectly. > > Do we really need to get these in 5.9 ? As these are significant changes and may > cause more bugs. Won't getting them in 5.9-stable and 5.10-rc1 be enough ? Yes we want these in v5.9 ideally but yes we could merge to 5.9-stable once accepted into the mainline. Jon -- nvpublic
Powered by blists - more mailing lists