All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Brian Masney <bmasney@redhat.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v3 10/15] clk: samsung: acpm: use clk_determine_rate_noop()
Date: Wed, 6 May 2026 15:47:33 +0200	[thread overview]
Message-ID: <abd89f01-f079-4ffb-9719-575ea5e30add@kernel.org> (raw)
In-Reply-To: <20260505-clk-determine-rate-noop-v3-10-f3f829fbacdf@redhat.com>

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

<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

...

If a tag was not added on purpose, please state in the patch changelog
or cover letter why and what changed.
</form letter>

Last part is important.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-05-06 13:47 UTC|newest]

Thread overview: 26+ 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 ` 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   ` 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 [this message]
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-06  0:49   ` Brian Masney
2026-05-10 10:17   ` Vinod Koul
2026-05-10 10:17     ` Vinod Koul
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=abd89f01-f079-4ffb-9719-575ea5e30add@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=bmasney@redhat.com \
    --cc=cw00.choi@samsung.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=tudor.ambarus@linaro.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 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.