From: Stephen Boyd <sboyd@kernel.org>
To: Tony Lindgren <tony@atomide.com>, linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/3] clk: ti: Drop legacy compatibility clocks for am3
Date: Tue, 15 Mar 2022 14:18:10 -0700 [thread overview]
Message-ID: <20220315211812.CA39CC340E8@smtp.kernel.org> (raw)
In-Reply-To: <20220203085618.16043-2-tony@atomide.com>
Quoting Tony Lindgren (2022-02-03 00:56:16)
> We no longer have users for the compatibility clocks and we can drop them.
> These are old duplicate clocks for what we using.
>
> Cc: devicetree@vger.kernel.org
> Cc: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2022-03-15 21:18 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 [this message]
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
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=20220315211812.CA39CC340E8@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=t-kristo@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.