linux-kernel - Re: [PATCH] regulator: Add LTC3676 support

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: <20160812092120.GY9347@sirena.org.uk>
Date:	Fri, 12 Aug 2016 10:21:20 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Tim Harvey <tharvey@...eworks.com>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Jaffer Kapasi <jkapasi@...ear.com>
Subject: Re: [PATCH] regulator: Add LTC3676 support

On Thu, Aug 11, 2016 at 01:48:21PM -0700, Tim Harvey wrote:

> regulators must have a non-null ops field or they will fail
> registration so I can't just not assign it. What would be an
> appropriate ops structure for a always-on fixed regulator?

OK, empty is fine there.

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