linux-kernel - Re: [PATCH 1/1] regulator: max77620: check for valid regulator info

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: <20160628193029.GZ17217@sirena.org.uk>
Date:	Tue, 28 Jun 2016 20:30:29 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Venkat Reddy Talla <vreddytalla@...dia.com>
Cc:	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Laxman Dewangan <ldewangan@...dia.com>
Subject: Re: [PATCH 1/1] regulator: max77620: check for valid regulator info

On Tue, Jun 28, 2016 at 04:35:56AM +0000, Venkat Reddy Talla wrote:

> > This sounds like it's papering over a bug in the driver - the driver should be
> > able to instantiate without anything beyond the registration of the device.
> > What's the driver relying on from the DT?

> Sorry for confusion, there is no dependent on DTS entry, I mean, in probe
> SD4 regulator for MAX77620 PMIC is not registered with regulator core framework so
> Regulator info will be null.

OK, can you please clarify this in the changelog?

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