linux-kernel - Re: [RFC PATCH] cpufreq: dt-platdev: Fix module autoloading

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]

Message-ID: <20241125051504.nvw4lzr4emi2vpf7@vireshk-i7>
Date: Mon, 25 Nov 2024 10:45:04 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: Radu Rendec <rrendec@...hat.com>, robh@...nel.org, arnd@...aro.org,
	linux-kernel@...r.kernel.org, Zhipeng Wang <zhipeng.wang_1@....com>,
	Maxime Ripard <mripard@...nel.org>, javier@...hile0.org,
	"Rafael J. Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
	andreas@...nade.info
Subject: Re: [RFC PATCH] cpufreq: dt-platdev: Fix module autoloading

On 22-11-24, 18:09, Javier Martinez Canillas wrote:
> Agreed with this. Likely (1) is the easiest path and (2) would make the
> driver more aligned with the rest of the kernel (that have a list of OF
> device IDs to autoload / match instead of some custom logic).
> 
> But I guess that (2) would be riskier, since not adding a platform that
> uses v2 will cause a regression.

I am inclined to go with (1) here and have applied a patch from Andreas Kemnade,
which he sent sometime back. I have used your commit log though, since it was
more descriptive.

-- 
viresh