Linux clock framework development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Brian Masney <bmasney@redhat.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 13/15] phy: mediatek: phy-mtk-hdmi-mt2701: use clk_determine_rate_noop()
Date: Sun, 10 May 2026 15:47:51 +0530	[thread overview]
Message-ID: <agBbT6YF0qXhizpQ@vaman> (raw)
In-Reply-To: <20260505-clk-determine-rate-noop-v3-13-f3f829fbacdf@redhat.com>

On 05-05-26, 20:49, Brian Masney wrote:
> Drop the driver-specific empty determine_rate() function and use the new
> shared clk_determine_rate_noop() helper.

Acked-by: Vinod Koul <vkoul@kernel.org>


-- 
~Vinod

  reply	other threads:[~2026-05-10 10:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  0:48 [PATCH v3 00/15] clk: introduce clk_determine_rate_noop() and update drivers to use it Brian Masney
2026-05-06  0:48 ` [PATCH v3 01/15] clk: imx: scu: drop redundant init.ops variable assignment Brian Masney
2026-05-06  0:48 ` [PATCH v3 02/15] clk: add clk_determine_rate_noop() Brian Masney
2026-05-06  0:48 ` [PATCH v3 03/15] clk: hisilicon: hi3660-stub: use clk_determine_rate_noop() Brian Masney
2026-05-06  0:49 ` [PATCH v3 04/15] clk: imx: scu: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 05/15] clk: qcom: rpm: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 06/15] clk: qcom: rpmh: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 07/15] clk: qcom: smd-rpm: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 08/15] clk: renesas: rzg2l-cpg: " Brian Masney
2026-05-06  7:19   ` Geert Uytterhoeven
2026-05-06  0:49 ` [PATCH v3 09/15] clk: rp1: " Brian Masney
2026-05-06 10:05   ` Andrea della Porta
2026-05-06  0:49 ` [PATCH v3 10/15] clk: samsung: acpm: " Brian Masney
2026-05-06 11:55   ` Tudor Ambarus
2026-05-06 13:47   ` Krzysztof Kozlowski
2026-05-06 14:34     ` Brian Masney
2026-05-06  0:49 ` [PATCH v3 11/15] clk: scpi: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 12/15] clk: sprd: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 13/15] phy: mediatek: phy-mtk-hdmi-mt2701: " Brian Masney
2026-05-10 10:17   ` Vinod Koul [this message]
2026-05-06  0:49 ` [PATCH v3 14/15] pmdomain: mediatek: airoha: " Brian Masney
2026-05-06  0:49 ` [PATCH v3 15/15] pmdomain: mediatek: mtk-mfg: " Brian Masney

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=agBbT6YF0qXhizpQ@vaman \
    --to=vkoul@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bmasney@redhat.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=sboyd@kernel.org \
    /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