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] [day] [month] [year] [list]
Message-ID: <ZvJ0XIF8FW_HiM0I@finisterre.sirena.org.uk>
Date: Tue, 24 Sep 2024 10:12:12 +0200
From: Mark Brown <broonie@...nel.org>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jean Delvare <jdelvare@...e.com>,
	Guenter Roeck <linux@...ck-us.net>,
	Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
	linux-hwmon@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 2/5] regulator: core: remove machine init callback from
 config

On Fri, Sep 20, 2024 at 06:47:03PM +0200, Jerome Brunet wrote:
> The machine specific regulator_init() appears to be unused.
> It does not allow a lot of interactiona with the regulator framework,
> since nothing from the framework is passed along (desc, config,
> etc ...)
> 
> Machine specific init may also be done with the added init_cb() in
> the regulator description, so remove regulator_init().

This makes sense regardless of what happens with the rest of the series.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ