From: "Rob Herring (Arm)" <robh@kernel.org>
To: genevieve.chan@altera.com
Cc: Stephen Boyd <sboyd@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, Brian Masney <bmasney@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Dinh Nguyen <dinguyen@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH RESEND v2] dt-bindings: clock: agilex: mark mpu_l2ram_clk deprecated
Date: Fri, 4 Sep 2026 09:55:25 -0500 [thread overview]
Message-ID: <178853365461.721871.11051925278426014682.robh@kernel.org> (raw)
In-Reply-To: <20260904032849.10554-1-genevieve.chan@altera.com>
On Fri, 04 Sep 2026 11:28:49 +0800, genevieve.chan@altera.com wrote:
> From: Genevieve Chan <genevieve.chan@altera.com>
>
> Preliminary documentation referred to mpu_l2ram_clk, but that clock is
> now mpu_ccu_clk and is already represented by AGILEX_MPU_CCU_CLK.
> Keep AGILEX_MPU_L2RAM_CLK as a legacy ABI-preserved ID (do not use in
> new DTs).
>
> Fixes: 6b3c59780ed3 ("dt-bindings: documentation: add clock bindings information for Agilex")
> Cc: stable@vger.kernel.org # 5.8+
> Signed-off-by: Genevieve Chan <genevieve.chan@altera.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
> Changes in v2:
> - Remove comment on unused clock ID 42
> - Reword commit message
> ---
> include/dt-bindings/clock/agilex-clock.h | 1 +
> 1 file changed, 1 insertion(+)
>
Applied, thanks!
I dropped Fixes and stable tag. There's no need for this to go to
stable.
Rob
prev parent reply other threads:[~2026-09-04 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 3:28 [PATCH RESEND v2] dt-bindings: clock: agilex: mark mpu_l2ram_clk deprecated genevieve.chan
2026-09-04 14:55 ` Rob Herring (Arm) [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=178853365461.721871.11051925278426014682.robh@kernel.org \
--to=robh@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=genevieve.chan@altera.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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