Hi Samuel, On Tue, Jul 31, 2012 at 20:00:21, AnilKumar, Chimata wrote: > Hi Samuel, > > On Fri, Jul 27, 2012 at 18:18:17, Samuel Ortiz wrote: > > Hi Anilkumar, > > > > On Fri, Jul 20, 2012 at 03:00:01PM +0530, AnilKumar Ch wrote: > > > Regulator platform data handling was mistakenly added to MFD > > > driver. So we will see build errors if we compile MFD drivers > > > without CONFIG_REGULATOR. This patch moves regulator platform > > > data handling from TPS65217 MFD driver to regulator driver. > > > > > > This makes MFD driver independent of REGULATOR framework so > > > build error is fixed if CONFIG_REGULATOR is not set. > > > > > > drivers/built-in.o: In function `tps65217_probe': > > > tps65217.c:(.devinit.text+0x13e37): undefined reference > > > to `of_regulator_match' > > > > > > This patch is based on linux-next (20120720) tree > > > > > > Signed-off-by: AnilKumar Ch <anilkumar@xxxxxx> > > > --- > > > drivers/mfd/tps65217.c | 130 +++++++++++--------------------- > > > drivers/regulator/tps65217-regulator.c | 124 ++++++++++++++++++++++++++---- > > > include/linux/mfd/tps65217.h | 12 ++- > > > 3 files changed, 161 insertions(+), 105 deletions(-) > > It doesn't apply to my for-next branch. Could you please re-send this one > > after the merge window is closed ? I'll push that as part of the MFD fixes for > > 3.6. > > > > I fetch regulator tree and applied on top of for-next branch and it is cleanly > applied. > My bad I picked up wrong tree, I will send the new version (if require) based on "MFD for-next" tree once the merge window closed. Thanks, AnilKumar -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
