From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] clk: ti: couple of fixes towards 5.8
Date: Wed, 29 Apr 2020 15:21:42 -0700 [thread overview]
Message-ID: <20200429222142.GW37466@atomide.com> (raw)
In-Reply-To: <20200429131341.4697-1-t-kristo@ti.com>
* Tero Kristo <t-kristo@ti.com> [200429 13:14]:
> Hi,
>
> The issues fixed by these patches have been around for a while, so they
> can be picked up for 5.8.
>
> Patch #1 fixes a memory leak within composite clock registration, which
> is only visible on platforms actually using composite clocks;
> omap4/omap5.
OK great thanks for chasing that one down.
> Last two patches fix parenting of the l4-secure clocks for omap4/omap5,
> which was apparenly missed when the clkctrl data for these domains was
> created.
Oops sorry about that. Looks like I totally missed adding the source
clocks for those.
For the whole series:
Acked-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2020-04-29 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 13:13 [PATCH 0/3] clk: ti: couple of fixes towards 5.8 Tero Kristo
2020-04-29 13:13 ` [PATCH 1/3] clk: ti: composite: fix memory leak Tero Kristo
2020-05-14 19:54 ` Stephen Boyd
2020-04-29 13:13 ` [PATCH 2/3] clk: ti: omap4: Add proper parent clocks for l4-secure clocks Tero Kristo
2020-05-14 19:54 ` Stephen Boyd
2020-04-29 13:13 ` [PATCH 3/3] clk: ti: omap5: " Tero Kristo
2020-05-14 19:55 ` Stephen Boyd
2020-04-29 22:21 ` Tony Lindgren [this message]
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=20200429222142.GW37466@atomide.com \
--to=tony@atomide.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.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).