[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14430b872eff187b4a4c213f6db31e0a.sboyd@kernel.org>
Date: Mon, 22 Apr 2024 12:00:27 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Sudeep Holla <sudeep.holla@....com>
Cc: Cristian Marussi <cristian.marussi@....com>, Sudeep Holla <sudeep.holla@....com>, linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org, james.quinlan@...adcom.com, f.fainelli@...il.com, vincent.guittot@...aro.org, peng.fan@....nxp.com, michal.simek@....com, quic_sibis@...cinc.com, quic_nkela@...cinc.com, souvik.chakravarty@....com, mturquette@...libre.com
Subject: Re: [PATCH v3 0/5] Rework SCMI Clock driver clk_ops setup procedure
Quoting Sudeep Holla (2024-04-22 01:06:06)
> On Fri, Apr 19, 2024 at 07:08:54PM -0700, Stephen Boyd wrote:
> > Quoting Cristian Marussi (2024-04-15 09:36:44)
> > > Hi,
> > >
> > > a small series to review how the SCMI Clock driver chooses and sets up the
> > > CLK operations to associate to a clock when registering with CLK framework.
> >
> > Did you want me to merge this through clk tree?
>
> I am fine either way. You add:
>
> Reviewed-by: Sudeep Holla <sudeep.holla@....com>
>
> if you prefer to take it. Or else please provide your ack for me to
> take it via SCMI tree.
>
Ok I can take it then.
Powered by blists - more mailing lists