On 12/10/2014 09:13 PM, Lee Jones wrote: > On Wed, 10 Dec 2014, Beomho Seo wrote: > >> On 12/09/2014 11:01 PM, Lee Jones wrote: >>> On Tue, 09 Dec 2014, Beomho Seo wrote: >>> >>>> This patch adds a new driver for Richtek RT5033 driver. >>>> RT5033 is a Multifunction device which includes battery charger, fuel gauge, >>>> flash LED current source, LDO and synchronous Buck converter. It is interfaced >>>> to host controller using I2C interface. >>>> >>>> Cc: Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> >>>> Cc: Lee Jones <lee.jone@xxxxxxxxxx> >>>> Signed-off-by: Beomho Seo <beomho.seo@xxxxxxxxxxx> >>>> Acked-by: Chanwoo Choi <cw00.choi@xxxxxxxxxxx> >>>> --- >>>> drivers/mfd/Kconfig | 12 ++ >>>> drivers/mfd/Makefile | 1 + >>>> drivers/mfd/rt5033.c | 142 ++++++++++++++++++++ >>>> include/linux/mfd/rt5033-private.h | 260 ++++++++++++++++++++++++++++++++++++ >>>> include/linux/mfd/rt5033.h | 62 +++++++++ >>>> 5 files changed, 477 insertions(+) >>>> create mode 100644 drivers/mfd/rt5033.c >>>> create mode 100644 include/linux/mfd/rt5033-private.h >>>> create mode 100644 include/linux/mfd/rt5033.h >>> >>> Much better. >>> >>> For my own reference: >>> >>> Acked-by: Lee Jones <lee.jones@xxxxxxxxxx> >>> >>> So what's the plan with this set? >>> >> >> This patch have been made on for-next-mfd branch of your git repository. >> So I hope this patch to be merged at your git repository. >> Another patch set(RT5033 regulator driver) have been merged on for-next branch of regulator git repository. >> >> https://git.kernel.org/cgit/linux/kernel/git/broonie/regulator.git/commit/?h=for-next&id=b1917578fd5d8efa67afa05a0d6d7e323f2802da >> >> Other patches(about charger, fuelgague and devicetree doc) will be re-sent to each maintainers. > > Okay, so all patches are indipendant/othognal of each other for sure? > Yes, rt5033 core driver merge before other patches with no problem. It is do not have dependency other patches. Best regards, Beomho Seo -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
