From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: From: "Rafael J. Wysocki" To: Scott Wood Cc: Yuantian Tang , 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 15:29:06 +0200 Message-ID: <3794032.AoZL3DhM7U@vostro.rjw.lan> In-Reply-To: References: <1466058085-19353-1-git-send-email-oss@buserror.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" List-ID: 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@rjwysocki.net] > >> Sent: Thursday, June 30, 2016 10:24 AM > >> To: Yuantian Tang > >> 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 > >> > >> On Thursday, June 30, 2016 01:47:09 AM Yuantian Tang wrote: > >>>> -----Original Message----- > >>>> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net] > >>>> Sent: Thursday, June 30, 2016 9:47 AM > >>>> To: Yuantian Tang > >>>> 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 > >>>> > >>>> 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