linux-kernel - Re: [PATCH v1 2/4] regulator: tps65219: Update driver name

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: <23dd1912-31cf-4e99-8fb0-0fbd68eee8e2@sirena.org.uk>
Date: Tue, 17 Dec 2024 21:01:30 +0000
From: Mark Brown <broonie@...nel.org>
To: Shree Ramamoorthy <s-ramamoorthy@...com>
Cc: aaro.koskinen@....fi, andreas@...nade.info, khilman@...libre.com,
	rogerq@...nel.org, tony@...mide.com, lgirdwood@...il.com,
	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	m-leonard@...com, praneeth@...com
Subject: Re: [PATCH v1 2/4] regulator: tps65219: Update driver name

On Tue, Dec 17, 2024 at 02:45:24PM -0600, Shree Ramamoorthy wrote:

> Follow the same naming convention in tps6594-regulator.c with
> tpsxxx-regulator instead of tpsxxx-pmic.

>  static struct platform_driver tps65219_regulator_driver = {
>  	.driver = {
> -		.name = "tps65219-pmic",
> +		.name = "tps65219-regulator",
>  		.probe_type = PROBE_PREFER_ASYNCHRONOUS,

This isn't just a naming convention thing AFACIT, the MFD registers the
new name so the driver wouldn't previously have loaded.  How did this
ever work?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)