Linux clock framework development
 help / color / mirror / Atom feed
From: "Chan, Genevieve" <genevieve.chan@altera.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney@redhat.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dinh Nguyen <dinguyen@kernel.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: linux driver reviews <linux-drivers-review@altera.com>
Subject: Re: [PATCH] dt-bindings: clock: agilex: mark mpu_l2ram_clk deprecated
Date: Fri, 7 Aug 2026 12:03:41 +0800	[thread overview]
Message-ID: <e80d3813-ad95-48a4-a748-c0ca0d8a2a86@altera.com> (raw)
In-Reply-To: <03c1b493-8296-4818-b00a-70a51cf5e39f@kernel.org>

On 6/8/2026 5:58 pm, Krzysztof Kozlowski wrote:
> [You don't often get email from krzk@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> On 27/07/2026 11:49, 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) and mark clock ID 42 as reserved/unused so it is not reused,
>> keeping all existing clock IDs stable for DT ABI compatibility.
>>
> Why are you Cc-ing non-functional addresses like
> "<linux-drivers-review@altera.com>"?
> 
> This bounces!
> 
> "Your message to linux-drivers-review@altera.com couldn't be delivered."
> 
> Best regards,
> Krzysztof

Hi,

V2 Patch is submitted and removed the non-functional addresses: 
https://lore.kernel.org/all/20260807035833.16198-1-genevieve.chan@altera.com/


      reply	other threads:[~2026-08-07  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  9:49 [PATCH] dt-bindings: clock: agilex: mark mpu_l2ram_clk deprecated genevieve.chan
2026-08-04  7:49 ` Krzysztof Kozlowski
2026-08-06  7:43   ` Chan, Genevieve
2026-08-06  7:58     ` Krzysztof Kozlowski
2026-08-06  9:58 ` Krzysztof Kozlowski
2026-08-07  4:03   ` Chan, Genevieve [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=e80d3813-ad95-48a4-a748-c0ca0d8a2a86@altera.com \
    --to=genevieve.chan@altera.com \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-drivers-review@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --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