From: Neil Armstrong <narmstrong@baylibre.com>
To: khilman@baylibre.com
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [RESEND PATCH v2 12/14] arm64: dts: meson-gxbb-nanopi-k2: add missing model
Date: Fri, 23 Aug 2019 09:02:46 +0200 [thread overview]
Message-ID: <20190823070248.25832-13-narmstrong@baylibre.com> (raw)
In-Reply-To: <20190823070248.25832-1-narmstrong@baylibre.com>
This fixes the following DT schemas check errors:
meson-gxbb-nanopi-k2.dt.yaml: /: 'model' is a required property
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
---
arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts
index c34c1c90ccb6..233eb1cd7967 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dts
@@ -10,6 +10,7 @@
/ {
compatible = "friendlyarm,nanopi-k2", "amlogic,meson-gxbb";
+ model = "FriendlyARM NanoPi K2";
aliases {
serial0 = &uart_AO;
--
2.22.0
next prev parent reply other threads:[~2019-08-23 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 7:02 [RESEND PATCH v2 00/14] arm64: dts: meson: fixes following YAML bindings schemas conversion Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 01/14] arm64: dts: meson: fix ethernet mac reg format Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 02/14] arm64: dts: meson-gx: drop the vpu dmc memory cell Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 03/14] arm64: dts: meson-gx: fix reset controller compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 04/14] arm64: dts: meson-gx: fix spifc compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 05/14] arm64: dts: meson-gx: fix watchdog compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 06/14] arm64: dts: meson-gx: fix mhu compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 07/14] arm64: dts: meson-gx: fix periphs bus node name Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 08/14] arm64: dts: meson-gxl: fix internal phy compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 09/14] arm64: dts: meson-axg: fix MHU compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 10/14] arm64: dts: meson-g12a: fix reset controller compatible Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 11/14] arm64: dts: meson-g12a-x96-max: fix compatible Neil Armstrong
2019-08-23 7:02 ` Neil Armstrong [this message]
2019-08-23 7:02 ` [RESEND PATCH v2 13/14] arm64: dts: meson-gxbb-p201: fix snps, reset-delays-us format Neil Armstrong
2019-08-23 7:02 ` [RESEND PATCH v2 14/14] arm64: dts: meson: fix boards regulators states format Neil Armstrong
2019-08-27 21:59 ` [RESEND PATCH v2 00/14] arm64: dts: meson: fixes following YAML bindings schemas conversion Kevin Hilman
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=20190823070248.25832-13-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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;
as well as URLs for NNTP newsgroup(s).