[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154344240618.88331.16995563056122948942@swboyd.mtv.corp.google.com>
Date: Wed, 28 Nov 2018 14:00:06 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Gregory CLEMENT <gregory.clement@...tlin.com>
Cc: Mike Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-arm-kernel@...ts.infradead.org,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Antoine Tenart <antoine.tenart@...tlin.com>,
Miquèl Raynal <miquel.raynal@...tlin.com>,
Maxime Chevallier <maxime.chevallier@...tlin.com>
Subject: Re: [PATCH 4/6] clk: mvebu: ap806: Fix clock name for the cluster
Quoting Gregory CLEMENT (2018-11-23 06:42:24)
> Hi Stephen,
>
> On mer., oct. 17 2018, Stephen Boyd <sboyd@...nel.org> wrote:
>
> > Quoting Gregory CLEMENT (2018-09-22 11:17:07)
> >> Actually, the clocks exposed for the cluster are not the CPU clocks, but
> >> the PLL clock used as entry clock for the CPU clocks. The CPU clock will
> >> be managed by a driver submitting in the following patches.
> >>
> >> Signed-off-by: Gregory CLEMENT <gregory.clement@...tlin.com>
> >
> > Does this need a fixes tag?
>
> It doesn't fix a regression so I don't thing it needs a fixes tag.
>
Would it help anyone who is backporting the stack of patches to support
this? I would liberally add a Fixes tag here in case it helps anyone
learn that this was incorrect all along.
Powered by blists - more mailing lists