-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
|> I suggest dealing with this by providing a standard regulator API |> set_power() in the s3cmci driver that platforms which use regulators can |> assign in their platform data. This avoids people rewriting the |> standard regulator API implementation. | | That sounds good to me. It would also remove the above discomfort, | because you'd only call it if you're sure there is a regulator. | | Thanks a lot for explaining ! Mmm, as I said but without the mugging: ''we can migrate regulator stuff entirely out of that file using the existing callback.''. It's kind of Mark to bother to answer but I think we can probably take a pee ourselves without involving someone upstream. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmK6JkACgkQOjLpvpq7dMpPOgCeIpoEs1sc8kXsgukIckNcY/jP EWsAn28JUaKpIRj/Hf4m7ksOKsF7r0BH =UhKR -----END PGP SIGNATURE-----
