linux/drivers/regulator, branch v3.8

Merge remote-tracking branch 'regulator/fix/tps65910' into tmp

2013-02-06T11:28:53Z

Merge remote-tracking branch 'regulator/fix/tps65217' into tmp

2013-02-06T11:28:52Z

Merge remote-tracking branch 'regulator/fix/s2mps11' into tmp

2013-02-06T11:28:51Z

Merge remote-tracking branch 'regulator/fix/of' into tmp

2013-02-06T11:28:51Z

Merge remote-tracking branch 'regulator/fix/max8998' into tmp

2013-02-06T11:28:50Z

Merge remote-tracking branch 'regulator/fix/max8997' into tmp

2013-02-06T11:28:49Z

Merge remote-tracking branch 'regulator/fix/max8907' into tmp

2013-02-06T11:28:48Z

Merge remote-tracking branch 'regulator/fix/max77686' into tmp

2013-02-06T11:28:48Z

regulator: s2mps11: fix incorrect register for buck10

2013-01-31T06:45:11Z

For BUCK10 the control registers are wrongly set as buck9 control register This patch corrects the control registers for buck10 Signed-off-by: Alim Akhtar Signed-off-by: Mark Brown Cc: stable@vger.kernel.org

regulator: clear state each invocation of of_regulator_match

2013-01-30T02:11:06Z

of_regulator_match() saves some dynamcially allocated state into the match table that's passed to it. By implementation and not contract, for each match table entry, if non-NULL state is already present, of_regulator_match() will not overwrite it. of_regulator_match() is typically called each time a regulator is probe()d. This means it is called with the same match table over and over again if a regulator triggers deferred probe. This results in stale, kfree()d data being left in the match table from probe to probe, which causes a variety of crashes or use of invalid data. Explicitly free all output state from of_regulator_match() before generating new results in order to avoid this. Signed-off-by: Stephen Warren Signed-off-by: Mark Brown Cc: stable@vger.kernel.org