aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-09-26 00:46:13 +0200
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-10-10 20:00:34 +0200
commitc98819a9e6904717a5c8672a0bfa173a0503eba1 (patch)
tree1db3e0284faf98de8f3ee37a6dd89a9ffaab9fce /target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts
parentc0aea384366002b113c7e89dfc704f1c3ce25c4e (diff)
downloadupstream-c98819a9e6904717a5c8672a0bfa173a0503eba1.tar.gz
upstream-c98819a9e6904717a5c8672a0bfa173a0503eba1.tar.bz2
upstream-c98819a9e6904717a5c8672a0bfa173a0503eba1.zip
bcm63xx: move dts-v1 statement to top-level DTSI files
The "/dts-v1/;" identifier is supposed to be present once at the top of a device tree file after the includes have been processed. Like done for other targets recently, put the dts-v1 statement into the top-level SoC-based DTSI files, and remove all other occurences. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts')
-rw-r--r--target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts2
1 files changed, 0 insertions, 2 deletions
diff --git a/target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts b/target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts
index 198f30cccf..50c57d5271 100644
--- a/target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts
+++ b/target/linux/bcm63xx/dts/bcm6368-brcm-bcm96368mvngr.dts
@@ -1,5 +1,3 @@
-/dts-v1/;
-
#include "bcm6368.dtsi"
#include <dt-bindings/input/input.h>