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

From: "Rafael J. Wysocki" <[email-masked]>
Date: Thu, 30 Jun 2016 04:24:29 +0200

On Thursday, June 30, 2016 01:47:09 AM Yuantian Tang wrote:
> > -----Original Message-----
> > From: Rafael J. Wysocki [mailto:[email-masked]]
> > Sent: Thursday, June 30, 2016 9:47 AM
> > To: Yuantian Tang <[email-masked]>
> > Cc: Scott Wood <[email-masked]>; Russell King <[email-masked]>;
> > Michael Turquette <[email-masked]>; Stephen Boyd
> > <[email-masked]>; Viresh Kumar <[email-masked]>; linux-
> > [email-masked]; [email-masked]; linuxppc-
> > [email-masked]; Yang-Leo Li <[email-masked]>; Xiaofeng Ren
> > <[email-masked]>; Scott Wood <[email-masked]>
> > 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.

Thanks,
Rafael