linux-kernel - Re: [PATCH 2/2] regulator: max8660: Add error message for missing regulator data

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: <20150324170752.GQ17265@sirena.org.uk>
Date:	Tue, 24 Mar 2015 10:07:52 -0700
From:	Mark Brown <broonie@...nel.org>
To:	Markus Pargmann <mpa@...gutronix.de>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	Wolfram Sang <wsa@...-dreams.de>, kernel@...gutronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] regulator: max8660: Add error message for missing
 regulator data

On Tue, Mar 24, 2015 at 05:40:11PM +0100, Markus Pargmann wrote:
> On Tue, Mar 24, 2015 at 09:08:57AM -0700, Mark Brown wrote:

> > Why is the platform data mandatory?  In general the goal is that a
> > regulator driver should be able to probe with no platform data.

> subdevs[]->platform_data is a struct regulator_init_data which has to
> exist so we can register the regulator later.

No, that's not the case.  The regulator API does not require that one be
provided in order to support the above use case.

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