From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v2 4/4] docs: dt: writing-schema: Document preferred order of properties
Date: Sun, 13 Jul 2025 14:46:39 +0200 [thread overview]
Message-ID: <20250713-dt-bindings-docs-v2-4-672c898054ae@linaro.org> (raw)
In-Reply-To: <20250713-dt-bindings-docs-v2-0-672c898054ae@linaro.org>
Document established Devicetree bindings maintainers review practice:
using DTS coding style property order in both 'properties' and
'required' secions.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
Changes in v2:
1. New patch
---
Documentation/devicetree/bindings/writing-schema.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/writing-schema.rst b/Documentation/devicetree/bindings/writing-schema.rst
index fc73072f12fc58dbaf3dea3eb8cc79cfac0341c8..470d1521fa174f4fac29004b95a9b1a8c37071d9 100644
--- a/Documentation/devicetree/bindings/writing-schema.rst
+++ b/Documentation/devicetree/bindings/writing-schema.rst
@@ -171,6 +171,9 @@ Coding style
Use YAML coding style (two-space indentation). For DTS examples in the schema,
preferred is four-space indentation.
+Place entries in 'properties' and 'required' sections in the same order, using
+style from Documentation/devicetree/bindings/dts-coding-style.rst.
+
Testing
-------
--
2.43.0
next prev parent reply other threads:[~2025-07-13 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 12:46 [PATCH v2 0/4] docs: dt: Document established practices: compatible and file naming, subjects Krzysztof Kozlowski
2025-07-13 12:46 ` [PATCH v2 1/4] docs: dt: submitting-patches: Avoid 'YAML' in the subject and add an example Krzysztof Kozlowski
2025-07-14 17:19 ` Conor Dooley
2025-07-14 21:22 ` Rob Herring (Arm)
2025-07-13 12:46 ` [PATCH v2 2/4] docs: dt: writing-bindings: Document compatible and filename naming Krzysztof Kozlowski
2025-07-14 17:20 ` Conor Dooley
2025-07-14 21:22 ` Rob Herring (Arm)
2025-07-13 12:46 ` [PATCH v2 3/4] docs: dt: writing-bindings: Document discouraged instance IDs Krzysztof Kozlowski
2025-07-14 17:20 ` Conor Dooley
2025-07-14 21:22 ` Rob Herring (Arm)
2025-07-13 12:46 ` Krzysztof Kozlowski [this message]
2025-07-14 17:20 ` [PATCH v2 4/4] docs: dt: writing-schema: Document preferred order of properties Conor Dooley
2025-07-14 21:23 ` Rob Herring (Arm)
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=20250713-dt-bindings-docs-v2-4-672c898054ae@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).