linux-kernel - Re: [PATCH] regulator: tps51632: Get regulator name from i2c

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]

Date:	Tue, 18 Jun 2013 12:44:36 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Mikko Perttunen <mperttunen@...dia.com>
Cc:	wsa@...-dreams.de, linux-tegra@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	linus.walleij@...aro.org
Subject: Re: [PATCH] regulator: tps51632: Get regulator name from i2c_client

On Tue, Jun 18, 2013 at 01:30:13PM +0300, Mikko Perttunen wrote:
> Commit "i2c: core: make it possible to match a pure device tree driver"
> changed semantics of the i2c probing for device tree devices.
> Device tree probed devices now get a NULL i2c_device_id pointer.
> This causes the regulator name to be set to NULL and the regulator
> registration to fail.

Applied, thanks.  Though it does seem like we should just be hard coding
this string anyway...

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