Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1461029
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] regulator: Add LTC3676 support |
| Date | 2016-08-12 11:30 +0200 |
| Message-ID | <s5gWS-8h2-5@gated-at.bofh.it> (permalink) |
| References | <s4oMO-5I4-17@gated-at.bofh.it> <s4GTp-n4-93@gated-at.bofh.it> <s4Mm5-413-11@gated-at.bofh.it> <s4UMF-24i-7@gated-at.bofh.it> <s555n-nU-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH] regulator: Add LTC3676 support Tim Harvey <tharvey@gateworks.com> - 2016-08-11 02:50 +0200
Re: [PATCH] regulator: Add LTC3676 support Mark Brown <broonie@kernel.org> - 2016-08-11 11:50 +0200
Re: [PATCH] regulator: Add LTC3676 support Tim Harvey <tharvey@gateworks.com> - 2016-08-11 22:50 +0200
Re: [PATCH] regulator: Add LTC3676 support Mark Brown <broonie@kernel.org> - 2016-08-12 11:30 +0200
csiph-web