From: Thierry Reding <thierry.reding@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Bjorn Andersson <andersson@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Heiko Stuebner <heiko@sntech.de>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Tero Kristo <kristo@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 7/7] clk: ti: clean-up simple provider misuse of the consumer API
Date: Mon, 27 Jul 2026 17:38:01 +0200 [thread overview]
Message-ID: <amd7U863RajvO4U6@orome> (raw)
In-Reply-To: <20260724-clk-provider-simple-clean-v2-7-56f306156d25@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Fri, Jul 24, 2026 at 11:03:58AM +0200, Jerome Brunet wrote:
> Clock provider should not be using the consumer interface.
> In other words, a provider should not be dealing with struct clk.
>
> This change targets occurrences for which the provider uses the
> consumer interface and corresponding clk_hw interface exist.
>
> Reviewed-by: Brian Masney <bmasney@redhat.com>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> drivers/clk/ti/clockdomain.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-27 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:03 [PATCH v2 0/7] clk: clean-up simple provider misuse of the consumer API Jerome Brunet
2026-07-24 9:03 ` [PATCH v2 1/7] clk: mvebu: " Jerome Brunet
2026-07-27 15:34 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 2/7] clk: qcom: " Jerome Brunet
2026-07-24 12:22 ` Konrad Dybcio
2026-07-27 15:35 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 3/7] clk: renesas: " Jerome Brunet
2026-07-27 15:35 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 4/7] clk: rockchip: " Jerome Brunet
2026-07-27 15:36 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 5/7] clk: st: " Jerome Brunet
2026-07-27 15:37 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 6/7] clk: tegra: " Jerome Brunet
2026-07-27 15:37 ` Thierry Reding
2026-07-24 9:03 ` [PATCH v2 7/7] clk: ti: " Jerome Brunet
2026-07-27 15:38 ` Thierry Reding [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=amd7U863RajvO4U6@orome \
--to=thierry.reding@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=bmasney@redhat.com \
--cc=geert+renesas@glider.be \
--cc=gregory.clement@bootlin.com \
--cc=heiko@sntech.de \
--cc=jbrunet@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.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