On Tue, 12 May 2020 at 17:09, Greg Ungerer <gregungerer@xxxxxxxxxxxxxx> wrote: > > Hi Ulf, > > On 7/5/20 7:13 pm, Ulf Hansson wrote: > > + Geert > > > > On Sat, 2 May 2020 at 01:54, Angelo Dureghello > > <angelo.dureghello@xxxxxxxxxxx> wrote: > >> > >> Add support for sdhci-edshc mmc controller. > >> > >> Signed-off-by: Angelo Dureghello <angelo.dureghello@xxxxxxxxxxx> > >> --- > >> Changes for v3: > >> - removed volatile cast from clk.c > >> --- > >> arch/m68k/coldfire/clk.c | 15 ++++++++++ > >> arch/m68k/coldfire/device.c | 33 +++++++++++++++++++-- > >> arch/m68k/coldfire/m5441x.c | 12 +++++++- > >> arch/m68k/include/asm/m5441xsim.h | 19 ++++++++++++ > >> arch/m68k/include/asm/mcfclk.h | 2 ++ > >> include/linux/platform_data/mmc-esdhc-mcf.h | 17 +++++++++++ > >> 6 files changed, 95 insertions(+), 3 deletions(-) > >> create mode 100644 include/linux/platform_data/mmc-esdhc-mcf.h > > > > Not sure what's the best way to deal with this patch. I looped in > > Geert to get some input. > > > > If it looks okay and the risk is minimal for conflicts, I can carry it > > via my tree, but then I need an ack from Geert. > > I can carry just this patch in the m68knommu git tree it you prefer. > Should be no conflicts that way. But really if you want to carry it > with all the others I don't have a problem with that either. It looks like the new platform data header file is being used by the mmc patch in 3/3, so it's probably easiest if I take them all via my mmc tree. Anyway, I will wait for a v4 from Angelo to address the comments. [...] Kind regards Uffe
