From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Scott Wood To: Yuantian Tang , "Rafael J. Wysocki" CC: Scott Wood , Russell King , Michael Turquette , Stephen Boyd , Viresh Kumar , "linux-clk@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , Yang-Leo Li , Xiaofeng Ren , Scott Wood Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering possible parent clocks Date: Thu, 30 Jun 2016 05:46:42 +0000 Message-ID: References: <1466058085-19353-1-git-send-email-oss@buserror.net> <2091721.Cm4CVR1ptK@vostro.rjw.lan> <2040199.AxgevOCPID@vostro.rjw.lan> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 List-ID: On 06/29/2016 10:02 PM, Yuantian Tang wrote:=0A= >> -----Original Message-----=0A= >> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]=0A= >> Sent: Thursday, June 30, 2016 10:24 AM=0A= >> To: Yuantian Tang =0A= >> Cc: Scott Wood ; Russell King ;= =0A= >> Michael Turquette ; Stephen Boyd=0A= >> ; Viresh Kumar ; linux-= =0A= >> clk@vger.kernel.org; linux-pm@vger.kernel.org; linuxppc-=0A= >> dev@lists.ozlabs.org; Yang-Leo Li ; Xiaofeng Ren=0A= >> ; Scott Wood =0A= >> Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering possi= ble=0A= >> parent clocks=0A= >>=0A= >> On Thursday, June 30, 2016 01:47:09 AM Yuantian Tang wrote:=0A= >>>> -----Original Message-----=0A= >>>> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]=0A= >>>> Sent: Thursday, June 30, 2016 9:47 AM=0A= >>>> To: Yuantian Tang =0A= >>>> Cc: Scott Wood ; Russell King=0A= >>>> ; Michael Turquette=0A= >>>> ; Stephen Boyd ;=0A= >>>> Viresh Kumar ; linux- clk@vger.kernel.org;=0A= >>>> linux-pm@vger.kernel.org; linuxppc- dev@lists.ozlabs.org; Yang-Leo=0A= >>>> Li ; Xiaofeng Ren ; Scott=0A= >>>> Wood =0A= >>>> Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering=0A= >>>> possible parent clocks=0A= >>>>=0A= >>>> On Wednesday, June 29, 2016 05:50:26 AM Yuantian Tang wrote:=0A= >>>>> Hi,=0A= >>>>>=0A= >>>>> This patch is acked by clock maintainer. If no comments from=0A= >>>>> anyone else,=0A= >>>> we will merge it in next week.=0A= >>>>=0A= >>>> There is a cpufreq commit depending on it. Are you going to handle=0A= >>>> that one too?=0A= >>>>=0A= >>> That one has been acked by cpufreq maintainer. You can get this from=0A= >> patch comments.=0A= >>=0A= >> I know that it has been ACKed.=0A= >>=0A= >> My question is whether or not you are going to apply it along the [1/2].= =0A= >>=0A= >> If not, it will have to be deferred until the [1/2] is merged and then a= pplied=0A= >> which may not be desirable.=0A= >>=0A= > I hope we can apply both at same time. Seems Scott has a few concerns.=0A= > =0A= > What you think about this patch? Can you apply it?=0A= > If you have applied this patch, then I can push CPUfreq maintainer to app= ly another one which will be delayed.=0A= =0A= My only concern was getting an ack for this patch (1/2) -- did I miss it=0A= somewhere?=0A= =0A= -Scott=0A= =0A=