On 08/30, Ulf Hansson wrote: > On 30 August 2017 at 14:36, Maxime Ripard > <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: > > Hi Ulf, > > > > On Wed, Aug 30, 2017 at 02:29:24PM +0200, Ulf Hansson wrote: > >> On 25 August 2017 at 11:49, Maxime Ripard > >> <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: > >> > The reset hook was left implemented. Provide a dumb implementation so that > >> > client drivers can depend on it. > >> > > >> > Signed-off-by: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> > >> > >> Do you want me to pick this up via my mmc tree? If so, is that okay by > >> the clock maintainers? > > > > I also happen to be the maintainer of that part of the kernel > > (reporting to Mike and Stephen of course). We don't have anything > > touching that file in next, so unless they feel like it should go > > through their tree, it would be easier to keep the two changes > > together and merge them through your tree. > > Alright, I have picked it up for next! > Thanks! Acked-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> if that helps. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
