linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Suman Anna <s-anna@ti.com>
Subject: [PATCH] dt-bindings: remoteproc: qcom: pas: Fix indentation warnings
Date: Thu, 3 Jun 2021 09:26:39 -0500	[thread overview]
Message-ID: <20210603142639.8335-1-s-anna@ti.com> (raw)

The list indentation should always be 2 spaces more than the preceding
keyword. A few of the items are only using 1 space, and resulting in
warnings with dt_binding_check. Fix these.

Fixes: cf107e98d024 ("dt-bindings: remoteproc: qcom: pas: Convert binding to YAML")
Signed-off-by: Suman Anna <s-anna@ti.com>
---
Hi Bjorn,

This patch is for you to pick up since you staged the corresponding YAML
conversion patch. Issue found when double-checking one of my bindings on
latest next.

regards
Suman

 .../bindings/remoteproc/qcom,adsp.yaml        | 38 +++++++++----------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
index 6c11812385ca..9ea05e608bc1 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
@@ -329,7 +329,7 @@ allOf:
             - description: CX power domain
         power-domain-names:
           items:
-           - const: cx
+            - const: cx
 
   - if:
       properties:
@@ -345,7 +345,7 @@ allOf:
             - description: SSC-CX power domain
         power-domain-names:
           items:
-           - const: ssc_cx
+            - const: ssc_cx
       required:
         - px-supply
 
@@ -365,10 +365,10 @@ allOf:
             - description: MSS power domain
         power-domain-names:
           items:
-           - const: load_state
-           - const: cx
-           - const: mx
-           - const: mss
+            - const: load_state
+            - const: cx
+            - const: mx
+            - const: mss
 
   - if:
       properties:
@@ -385,8 +385,8 @@ allOf:
             - description: CX power domain
         power-domain-names:
           items:
-           - const: load_state
-           - const: cx
+            - const: load_state
+            - const: cx
 
   - if:
       properties:
@@ -404,9 +404,9 @@ allOf:
             - description: MSS power domain
         power-domain-names:
           items:
-           - const: load_state
-           - const: cx
-           - const: mss
+            - const: load_state
+            - const: cx
+            - const: mss
 
   - if:
       properties:
@@ -422,8 +422,8 @@ allOf:
             - description: MSS power domain
         power-domain-names:
           items:
-           - const: cx
-           - const: mss
+            - const: cx
+            - const: mss
 
   - if:
       properties:
@@ -444,9 +444,9 @@ allOf:
             - description: LMX power domain
         power-domain-names:
           items:
-           - const: load_state
-           - const: lcx
-           - const: lmx
+            - const: load_state
+            - const: lcx
+            - const: lmx
 
   - if:
       properties:
@@ -463,9 +463,9 @@ allOf:
             - description: MXC power domain
         power-domain-names:
           items:
-           - const: load_state
-           - const: cx
-           - const: mxc
+            - const: load_state
+            - const: cx
+            - const: mxc
 
   - if:
       properties:
-- 
2.30.1


                 reply	other threads:[~2021-06-03 14:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210603142639.8335-1-s-anna@ti.com \
    --to=s-anna@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=robh+dt@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).