From: Brian Masney <masneyb@onstation.org>
To: arnd@arndb.de
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
sugaya.taichi@socionext.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH] dt-bindings: arm: correct dt_binding_check parse error
Date: Sat, 30 Mar 2019 22:42:40 -0400 [thread overview]
Message-ID: <20190331024240.3012-1-masneyb@onstation.org> (raw)
'make dt_binding_check' fails with the following error:
Documentation/devicetree/bindings/arm/cpus.yaml: while scanning a
plain scalar
in "<unicode string>", line 231, column 19
found a tab character that violates indentation
in "<unicode string>", line 232, column 1
make[1]: *** [Documentation/devicetree/bindings/Makefile:12:
Documentation/devicetree/bindings/arm/cpus.example.dts] Error 1
Correct the parse error by replacing the tabs with spaces to keep
'make dt_binding_check' happy.
Signed-off-by: Brian Masney <masneyb@onstation.org>
Fixes: fd73403a4862 ("dt-bindings: arm: Add SMP enable-method for Milbeaut")
---
Issue is in linux-next-20190329.
Documentation/devicetree/bindings/arm/cpus.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index 60eab6dc3c0b..591bbd012d63 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -229,7 +229,7 @@ patternProperties:
- renesas,r9a06g032-smp
- rockchip,rk3036-smp
- rockchip,rk3066-smp
- - socionext,milbeaut-m10v-smp
+ - socionext,milbeaut-m10v-smp
- ste,dbx500-smp
cpu-release-addr:
--
2.20.1
next reply other threads:[~2019-03-31 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 2:42 Brian Masney [this message]
2019-04-01 6:07 ` 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=20190331024240.3012-1-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sugaya.taichi@socionext.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
all inboxes | Powered by JetHome®