diff options
| author | Stephen Warren <swarren@nvidia.com> | 2012-08-23 12:19:18 -0600 |
|---|---|---|
| committer | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2012-08-28 11:00:30 -0700 |
| commit | 5fc72f57e62e10d9d8347ae20f13820d811377da (patch) | |
| tree | f47209456bf767af3660bd727a5459fd79274fc2 /CREDITS | |
| parent | dedae957a41b4f4523199f7a822ee4e5735640b0 (diff) | |
| download | linux-stable-5fc72f57e62e10d9d8347ae20f13820d811377da.tar.gz linux-stable-5fc72f57e62e10d9d8347ae20f13820d811377da.tar.bz2 linux-stable-5fc72f57e62e10d9d8347ae20f13820d811377da.zip | |
regulator: max8907: fix use of possibly NULL idata
If a regulator is not used by a board, it's quite legitimate not to
provide platform data or a device tree node to configure it (i.e.
regulator_init_data). In that case, during MAX8907 regulator's
probe(), the idata variable will be NULL for that regulator. Prevent
dereferincing it.
If the MBATT regulator's init_data is not specified, or no name was
specified in the constraints, the regulator will be named based on
the regulator descriptor, so initialize mbatt_rail_name from there.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions