public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Saravana Kannan <saravanak@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: add DTS example style checker
Date: Tue, 21 Apr 2026 13:34:36 +0200	[thread overview]
Message-ID: <20260421-blazing-leopard-from-atlantis-bfeb0c@quoll> (raw)
In-Reply-To: <941c1ca0cd30c596556a88c36d28d60368867409.1776700167.git.daniel@makrotopia.org>

On Mon, Apr 20, 2026 at 04:50:27PM +0100, Daniel Golle wrote:
> Add a Python script that enforces coding style rules from
> dts-coding-style.rst on examples embedded in YAML binding files.
> 
> Checks indentation, property and child node ordering, blank line
> placement, node naming, tabs, trailing whitespace and unused labels.
> Produces a canonical form and diffs it against the original.

Thanks for working on this, I like it a lot.

I would be happy to see at least a few test cases for it - bad and good
binding examples here - so development will be easier.

Best regards,
Krzysztof


  reply	other threads:[~2026-04-21 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 15:50 [PATCH 0/2] dt-bindings: automated coding style check for DTS examples Daniel Golle
2026-04-20 15:50 ` [PATCH 1/2] dt-bindings: add DTS example style checker Daniel Golle
2026-04-21 11:34   ` Krzysztof Kozlowski [this message]
2026-04-20 15:50 ` [PATCH 2/2] dt-bindings: wire example style check into dt_binding_check Daniel Golle
2026-04-20 21:51 ` [PATCH 0/2] dt-bindings: automated coding style check for DTS examples 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=20260421-blazing-leopard-from-atlantis-bfeb0c@quoll \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=saravanak@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