[PATCH v3 1/2] clk: Add consumer APIs for discovering possible parent clocks

Rafael J. Wysocki rjw at rjwysocki.net
Thu Jun 30 23:29:06 AEST 2016


On Thursday, June 30, 2016 05:46:42 AM Scott Wood wrote:
> On 06/29/2016 10:02 PM, Yuantian Tang wrote:
> >> -----Original Message-----
> >> From: Rafael J. Wysocki [mailto:rjw at rjwysocki.net]
> >> Sent: Thursday, June 30, 2016 10:24 AM
> >> To: Yuantian Tang <yuantian.tang at nxp.com>
> >> Cc: Scott Wood <oss at buserror.net>; Russell King <linux at armlinux.org.uk>;
> >> Michael Turquette <mturquette at baylibre.com>; Stephen Boyd
> >> <sboyd at codeaurora.org>; Viresh Kumar <viresh.kumar at linaro.org>; linux-
> >> clk at vger.kernel.org; linux-pm at vger.kernel.org; linuxppc-
> >> dev at lists.ozlabs.org; Yang-Leo Li <leoyang.li at nxp.com>; Xiaofeng Ren
> >> <xiaofeng.ren at nxp.com>; Scott Wood <scottwood at freescale.com>
> >> Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering possible
> >> parent clocks
> >>
> >> On Thursday, June 30, 2016 01:47:09 AM Yuantian Tang wrote:
> >>>> -----Original Message-----
> >>>> From: Rafael J. Wysocki [mailto:rjw at rjwysocki.net]
> >>>> Sent: Thursday, June 30, 2016 9:47 AM
> >>>> To: Yuantian Tang <yuantian.tang at nxp.com>
> >>>> Cc: Scott Wood <oss at buserror.net>; Russell King
> >>>> <linux at armlinux.org.uk>; Michael Turquette
> >>>> <mturquette at baylibre.com>; Stephen Boyd <sboyd at codeaurora.org>;
> >>>> Viresh Kumar <viresh.kumar at linaro.org>; linux- clk at vger.kernel.org;
> >>>> linux-pm at vger.kernel.org; linuxppc- dev at lists.ozlabs.org; Yang-Leo
> >>>> Li <leoyang.li at nxp.com>; Xiaofeng Ren <xiaofeng.ren at nxp.com>; Scott
> >>>> Wood <scottwood at freescale.com>
> >>>> Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering
> >>>> possible parent clocks
> >>>>
> >>>> On Wednesday, June 29, 2016 05:50:26 AM Yuantian Tang wrote:
> >>>>> Hi,
> >>>>>
> >>>>> This patch is acked by clock maintainer. If no comments from
> >>>>> anyone else,
> >>>> we will merge it in next week.
> >>>>
> >>>> There is a cpufreq commit depending on it.  Are you going to handle
> >>>> that one too?
> >>>>
> >>> That one has been acked by cpufreq maintainer. You can get this from
> >> patch comments.
> >>
> >> I know that it has been ACKed.
> >>
> >> My question is whether or not you are going to apply it along the [1/2].
> >>
> >> If not, it will have to be deferred until the [1/2] is merged and then applied
> >> which may not be desirable.
> >>
> > I hope we can apply both at same time. Seems Scott has a few concerns.
> > 
> > What you think about this patch? Can you apply it?
> > If you have applied this patch, then I can push CPUfreq maintainer to apply another one which will be delayed.
> 
> My only concern was getting an ack for this patch (1/2) -- did I miss it
> somewhere?

OK, so who's going to apply the series?

Thanks,
Rafael



More information about the Linuxppc-dev mailing list