diff options
| author | Lars-Peter Clausen <lars@metafoo.de> | 2018-09-28 11:23:40 +0200 |
|---|---|---|
| committer | Jonathan Cameron <Jonathan.Cameron@huawei.com> | 2018-09-29 13:28:47 +0100 |
| commit | 8911a43bc198877fad9f4b0246a866b26bb547ab (patch) | |
| tree | 6d3de9e207c9713fc8eb53dfd12b7a24de97dd78 /MAINTAINERS | |
| parent | 827df0571fb32d308f26c34641c1a88ba500d28e (diff) | |
| download | linux-8911a43bc198877fad9f4b0246a866b26bb547ab.tar.gz linux-8911a43bc198877fad9f4b0246a866b26bb547ab.tar.bz2 linux-8911a43bc198877fad9f4b0246a866b26bb547ab.zip | |
iio: ad5064: Fix regulator handling
The correct way to handle errors returned by regualtor_get() and friends is
to propagate the error since that means that an regulator was specified,
but something went wrong when requesting it.
For handling optional regulators, e.g. when the device has an internal
vref, regulator_get_optional() should be used to avoid getting the dummy
regulator that the regulator core otherwise provides.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Cc: <Stable@vger.kernel.org>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions