From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] Drop TI compatibility clocks
Date: Sat, 12 Mar 2022 09:52:36 +0200 [thread overview]
Message-ID: <YixRREMd+t1tbbwC@atomide.com> (raw)
In-Reply-To: <20220311033617.5712AC340EE@smtp.kernel.org>
* Stephen Boyd <sboyd@kernel.org> [220311 03:34]:
> Quoting Tony Lindgren (2022-02-03 00:56:15)
> > Hi all,
> >
> > In order to prepare the TI clocks for fixing lots of devicetree warnings,
> > let's first drop the now unused compatibility clocks.
> >
> > The dra7 changes depend on my still pending omap-for-v5.17/fixes-not-urgent
> > pull request that did not make it for v5.17-rc series so far.
> >
>
> What should I do with this one though?
Well the dependencies are now merged to the mainline kernel, so you could
merge in commit 31aa7056bbec, then apply this series if otherwise OK.
Commit 31aa7056bbec is based on the old v5.16-rc1. It would bring few other
fixes from mainline too if pulled on a v5.17-rc1 based branch:
31aa7056bbec ("ARM: dts: Don't use legacy clock defines for dra7 clkctrl")
9206a3af4fc0 ("clk: ti: Move dra7 clock devices out of the legacy section")
23885389dbbb ("ARM: dts: Fix timer regression for beagleboard revision c")
29a5e8496b3a ("ARM: dts: am335x-wega: Fix typo in mcasp property rx-num-evt")
34596ba380b0 ("ARM: OMAP2+: adjust the location of put_device() call in omapdss_init_of")
80c469a0a037 ("ARM: OMAP2+: hwmod: Add of_node_put() before break")
Regards,
Tony
next prev parent reply other threads:[~2022-03-12 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:56 [PATCH 0/3] Drop TI compatibility clocks Tony Lindgren
2022-02-03 8:56 ` [PATCH 1/3] clk: ti: Drop legacy compatibility clocks for am3 Tony Lindgren
2022-02-11 13:45 ` Rob Herring
2022-03-15 21:18 ` Stephen Boyd
2022-02-03 8:56 ` [PATCH 2/3] clk: ti: Drop legacy compatibility clocks for am4 Tony Lindgren
2022-02-11 13:45 ` Rob Herring
2022-03-15 21:18 ` Stephen Boyd
2022-02-03 8:56 ` [PATCH 3/3] clk: ti: Drop legacy compatibility clocks for dra7 Tony Lindgren
2022-02-11 13:46 ` Rob Herring
2022-03-15 21:18 ` Stephen Boyd
2022-03-11 3:36 ` [PATCH 0/3] Drop TI compatibility clocks Stephen Boyd
2022-03-12 7:52 ` Tony Lindgren [this message]
2022-03-15 21:06 ` Stephen Boyd
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=YixRREMd+t1tbbwC@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--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).