linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 01/18] arm64: qcom: apq8016-sbc: drop qcom,sbc
Date: Mon,  8 Mar 2021 11:38:09 +0530	[thread overview]
Message-ID: <20210308060826.3074234-2-vkoul@kernel.org> (raw)
In-Reply-To: <20210308060826.3074234-1-vkoul@kernel.org>

apq8016-sbc is one of the compaitibles for this board, but is not
documented, so drop it. This fixes these two warns:

arch/arm64/boot/dts/qcom/apq8016-sbc.dt.yaml: /: compatible: ['qcom,apq8016-sbc', 'qcom,apq8016', 'qcom,sbc']
is not valid under any of the given schemas (Possible causes of the failure):

arch/arm64/boot/dts/qcom/apq8016-sbc.dt.yaml: /: compatible: ['qcom,apq8016-sbc', 'qcom,apq8016', 'qcom,sbc'] is too long
arch/arm64/boot/dts/qcom/apq8016-sbc.dt.yaml: /: compatible:0: 'qcom,apq8016-sbc'
is not one of ['qcom,apq8064-cm-qs600', 'qcom,apq8064-ifc6410']
arch/arm64/boot/dts/qcom/apq8016-sbc.dt.yaml: /: compatible:0: 'qcom,apq8016-sbc'
is not one of ['qcom,apq8074-dragonboard']

Signed-off-by: Vinod Koul <vkoul@kernel.org>
---
 arch/arm64/boot/dts/qcom/apq8016-sbc.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/qcom/apq8016-sbc.dts b/arch/arm64/boot/dts/qcom/apq8016-sbc.dts
index 48bd1c2874de..f3c0dbfd0a23 100644
--- a/arch/arm64/boot/dts/qcom/apq8016-sbc.dts
+++ b/arch/arm64/boot/dts/qcom/apq8016-sbc.dts
@@ -9,5 +9,5 @@
 
 / {
 	model = "Qualcomm Technologies, Inc. APQ 8016 SBC";
-	compatible = "qcom,apq8016-sbc", "qcom,apq8016", "qcom,sbc";
+	compatible = "qcom,apq8016-sbc", "qcom,apq8016";
 };
-- 
2.26.2


  reply	other threads:[~2021-03-08  6:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  6:08 [PATCH 00/18] arm64: qcom: fix dtbs_check warning Vinod Koul
2021-03-08  6:08 ` Vinod Koul [this message]
2021-03-08  6:08 ` [PATCH 02/18] arm64: qcom: msm8916: don't use empty memory node Vinod Koul
2021-03-08  6:08 ` [PATCH 03/18] dt-bindings: arm: qcom: Document ipq6018-cp01 board Vinod Koul
2021-03-08  6:08 ` [PATCH 04/18] arm64: qcom: msm8994: don't use empty memory node Vinod Koul
2021-03-08  6:08 ` [PATCH 05/18] dt-bindings: arm: qcom: Document sony boards for apq8094 Vinod Koul
2021-03-10 13:41   ` Konrad Dybcio
2021-03-08  6:08 ` [PATCH 06/18] dt-bindings: arm: qcom: Document alcatel,idol347 board Vinod Koul
2021-03-10 13:42   ` Konrad Dybcio
2021-03-08  6:08 ` [PATCH 07/18] dt-bindings: arm: qcom: Drop qcom,mtp Vinod Koul
2021-03-08  6:08 ` [PATCH 08/18] arm64: qcom: msm8994: don't use underscore in node name Vinod Koul
2021-03-08  6:08 ` [PATCH 09/18] arm64: qcom: msm8996: " Vinod Koul
2021-03-08  6:08 ` [PATCH 10/18] arm64: qcom: sdm630: " Vinod Koul
2021-03-08  6:08 ` [PATCH 11/18] arm64: qcom: sdm660: " Vinod Koul
2021-03-10 14:48   ` Konrad Dybcio
2021-03-08  6:08 ` [PATCH 12/18] arm64: qcom: msm8996: don't use empty memory node Vinod Koul
2021-03-10 14:46   ` Konrad Dybcio
2021-03-08  6:08 ` [PATCH 13/18] arm64: qcom: msm8998: " Vinod Koul
2021-03-08  6:08 ` [PATCH 14/18] arm64: qcom: sdm630: " Vinod Koul
2021-03-10 13:49   ` Konrad Dybcio
2021-03-08  6:08 ` [PATCH 15/18] arm64: qcom: sdm660: " Vinod Koul
2021-03-08  6:08 ` [PATCH 16/18] arm64: qcom: ipq8074: fix pci node reg property Vinod Koul
2021-03-08  6:08 ` [PATCH 17/18] arm64: qcom: sdm660: use reg value for memory node Vinod Koul
2021-03-08  6:08 ` [PATCH 18/18] arm64: qcom: ipq6018: drop '0x' from unit address Vinod Koul

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=20210308060826.3074234-2-vkoul@kernel.org \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).