devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Palmer <daniel@0x0f.com>,
	krzk+dt@kernel.org, romain.perier@gmail.com, robh@kernel.org,
	conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arm: dts: mstar: infinity: Correct opp table name
Date: Wed, 31 Dec 2025 08:47:56 +0100	[thread overview]
Message-ID: <ac0f8b8d-f6e4-4d60-9931-e820417c1abc@kernel.org> (raw)
In-Reply-To: <20251231025502.1139168-4-daniel@0x0f.com>

On 31/12/2025 03:55, Daniel Palmer wrote:
> The dt validation stuff expects the name of the opp table
> to match a regexp and it currently doesn't.
> 
> Update the name to match the regexp.
> 
> Signed-off-by: Daniel Palmer <daniel@0x0f.com>


These two should be squashed. Don't align node names with bindings per node.

Best regards,
Krzysztof

  reply	other threads:[~2025-12-31  7:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31  2:54 [PATCH 0/5] Sigmastar DT warnings fixing part 1 Daniel Palmer
2025-12-31  2:54 ` [PATCH 1/5] arm: dts: mstar: breadbee: Correct regulator names Daniel Palmer
2025-12-31  9:49   ` Krzysztof Kozlowski
2025-12-31  2:54 ` [PATCH 2/5] arm: dts: mstar: breadbee: Correct LED names Daniel Palmer
2025-12-31  2:55 ` [PATCH 3/5] arm: dts: mstar: infinity: Correct opp table name Daniel Palmer
2025-12-31  7:47   ` Krzysztof Kozlowski [this message]
2025-12-31  8:35     ` Daniel Palmer
2025-12-31  9:48       ` Krzysztof Kozlowski
2025-12-31 10:17         ` Daniel Palmer
2026-01-02 10:03           ` Krzysztof Kozlowski
2025-12-31  2:55 ` [PATCH 4/5] arm: dts: mstar: v7: Move the reboot node Daniel Palmer
2025-12-31  2:55 ` [PATCH 5/5] arm: dts: mstar: v7: Add sizes and ranges to sram Daniel Palmer
2026-01-02 14:43 ` [PATCH 0/5] Sigmastar DT warnings fixing part 1 Rob Herring

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=ac0f8b8d-f6e4-4d60-9931-e820417c1abc@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=romain.perier@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;
as well as URLs for NNTP newsgroup(s).