From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Scott Wood <oss@buserror.net>
Cc: Scott Wood <scott.wood@nxp.com>,
Yuantian Tang <yuantian.tang@nxp.com>,
Russell King <linux@armlinux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Yang-Leo Li <leoyang.li@nxp.com>,
Xiaofeng Ren <xiaofeng.ren@nxp.com>
Subject: Re: [PATCH v3 1/2] clk: Add consumer APIs for discovering possible parent clocks
Date: Fri, 01 Jul 2016 22:53:44 +0200 [thread overview]
Message-ID: <1736057.IZk9ncTkZk@vostro.rjw.lan> (raw)
In-Reply-To: <1467356146.32358.32.camel@buserror.net>
On Friday, July 01, 2016 01:55:46 AM Scott Wood wrote:
> On Thu, 2016-06-30 at 15:29 +0200, Rafael J. Wysocki wrote:
> > 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 <yuantian.tang@nxp.com>
> > > > > Cc: Scott Wood <oss@buserror.net>; Russell King <linux@armlinux.org.uk
> > > > > >;
> > > > > Michael Turquette <mturquette@baylibre.com>; Stephen Boyd
> > > > > <sboyd@codeaurora.org>; Viresh Kumar <viresh.kumar@linaro.org>; linux-
> > > > > clk@vger.kernel.org; linux-pm@vger.kernel.org; linuxppc-
> > > > > dev@lists.ozlabs.org; Yang-Leo Li <leoyang.li@nxp.com>; Xiaofeng Ren
> > > > > <xiaofeng.ren@nxp.com>; Scott Wood <scottwood@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@rjwysocki.net]
> > > > > > > Sent: Thursday, June 30, 2016 9:47 AM
> > > > > > > To: Yuantian Tang <yuantian.tang@nxp.com>
> > > > > > > Cc: Scott Wood <oss@buserror.net>; Russell King
> > > > > > > <linux@armlinux.org.uk>; Michael Turquette
> > > > > > > <mturquette@baylibre.com>; Stephen Boyd <sboyd@codeaurora.org>;
> > > > > > > Viresh Kumar <viresh.kumar@linaro.org>; linux- clk@vger.kernel.org
> > > > > > > ;
> > > > > > > linux-pm@vger.kernel.org; linuxppc- dev@lists.ozlabs.org; Yang-Leo
> > > > > > > Li <leoyang.li@nxp.com>; Xiaofeng Ren <xiaofeng.ren@nxp.com>;
> > > > > > > Scott
> > > > > > > Wood <scottwood@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?
>
> Ideally it should go via the cpufreq tree.
OK, I'll apply both, then.
Who exactly has ACKed the [1/2] from the clk side?
Thanks,
Rafael
next prev parent reply other threads:[~2016-07-01 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 6:21 [PATCH v3 1/2] clk: Add consumer APIs for discovering possible parent clocks Scott Wood
2016-06-16 6:21 ` [PATCH v3 2/2] cpufreq: qoriq: Don't look at clock implementation details Scott Wood
2016-07-07 1:30 ` Michael Turquette
2016-07-07 4:13 ` Scott Wood
2016-07-08 2:26 ` Michael Turquette
2016-07-08 21:06 ` Scott Wood
2016-07-20 3:02 ` Yuantian Tang
2017-02-02 18:11 ` Leo Li
2017-02-06 6:12 ` Y.T. Tang
2016-06-29 5:50 ` [PATCH v3 1/2] clk: Add consumer APIs for discovering possible parent clocks Yuantian Tang
2016-06-30 1:46 ` Rafael J. Wysocki
2016-06-30 1:47 ` Yuantian Tang
2016-06-30 2:24 ` Rafael J. Wysocki
2016-06-30 3:01 ` Yuantian Tang
2016-06-30 5:46 ` Scott Wood
2016-06-30 13:29 ` Rafael J. Wysocki
2016-07-01 6:55 ` Scott Wood
2016-07-01 20:53 ` Rafael J. Wysocki [this message]
2016-07-01 20:57 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1736057.IZk9ncTkZk@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=leoyang.li@nxp.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mturquette@baylibre.com \
--cc=oss@buserror.net \
--cc=sboyd@codeaurora.org \
--cc=scott.wood@nxp.com \
--cc=viresh.kumar@linaro.org \
--cc=xiaofeng.ren@nxp.com \
--cc=yuantian.tang@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).