From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D55A5C77B60 for ; Thu, 23 Mar 2023 13:59:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229964AbjCWN7G (ORCPT ); Thu, 23 Mar 2023 09:59:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231996AbjCWN6s (ORCPT ); Thu, 23 Mar 2023 09:58:48 -0400 Received: from mail-oa1-f46.google.com (mail-oa1-f46.google.com [209.85.160.46]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E8FA82685E; Thu, 23 Mar 2023 06:58:41 -0700 (PDT) Received: by mail-oa1-f46.google.com with SMTP id 586e51a60fabf-17ec8963db8so7375fac.8; Thu, 23 Mar 2023 06:58:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679579921; h=date:subject:message-id:references:in-reply-to:cc:to:from :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=3EdY5iCPNRdL2TyeF/Jo7q7w4WXQEC68Fw8bFxtFUC0=; b=gw0l4X4Hg0CUQuBES4DYIfpSLSTLKqQNUwrGwFLFM0fRw0X7OqOaMkrCBwgmzwyPO1 5P+Jc8Dpwu3w7JxO/d3u6ylXkbaLNAfOoyVFL9j99Lmvg+lN3jVtXj8lNZvB0BucV1PP qtDnfBm+gVrt2zR0qm/QeUdMt/iSkm9fnuz9e3SxB4WmmXTXZa/3mbpOa+YnsLSbAxZT dlOxbfYjEtprhuCt6re/hp4iVfwpNn/UTUYdyu8vhN5ZBGViQR0WIVF7y2s7PDk+iB2e 0Pi9L7Tuco76T8ZhTOXTT1sHEOAod4G60kd18yxopnoiK84vqxbhTC8YHxKt+8gSIdE5 A9CQ== X-Gm-Message-State: AAQBX9c+hsF96kJwkjDSztIvowMSy0ME3fvt4iZ8n0BM2Kl8ZjJNvRhv EspEDaSebfIr/+Yaux9Vxg== X-Google-Smtp-Source: AKy350ahvKVl/qTqdPvklQDydqu6nw60l4wULSmXqHKjZDmyQTqFM7vvOu4LY79a97GpbICq0EgPrQ== X-Received: by 2002:a05:6870:b006:b0:178:fe16:4e6c with SMTP id y6-20020a056870b00600b00178fe164e6cmr1979157oae.50.1679579921108; Thu, 23 Mar 2023 06:58:41 -0700 (PDT) Received: from robh_at_kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id vd21-20020a0568708f9500b0017ae1aede32sm6104388oab.46.2023.03.23.06.58.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Mar 2023 06:58:40 -0700 (PDT) Received: (nullmailer pid 3103740 invoked by uid 1000); Thu, 23 Mar 2023 13:58:37 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Rob Herring To: Neil Armstrong Cc: Lee Jones , Abhinav Kumar , David Airlie , Dmitry Baryshkov , Alim Akhtar , Rob Herring , Krzysztof Kozlowski , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Konrad Dybcio , Avri Altman , Sean Paul , freedreno@lists.freedesktop.org, Bjorn Andersson , Stephen Boyd , Manivannan Sadhasivam , Rob Clark , Daniel Vetter , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, Krzysztof Kozlowski , Andy Gross , linux-scsi@vger.kernel.org, Bart Van Assche In-Reply-To: <20230323-topic-sm8450-upstream-dt-bindings-fixes-v1-1-3ead1e418fe4@linaro.org> References: <20230323-topic-sm8450-upstream-dt-bindings-fixes-v1-0-3ead1e418fe4@linaro.org> <20230323-topic-sm8450-upstream-dt-bindings-fixes-v1-1-3ead1e418fe4@linaro.org> Message-Id: <167957963042.3095255.5445133387110199668.robh@kernel.org> Subject: Re: [PATCH 1/8] dt-bindings: display: msm: sm8450-mdss: Fix DSI compatible Date: Thu, 23 Mar 2023 08:58:37 -0500 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 23 Mar 2023 11:25:16 +0100, Neil Armstrong wrote: > The DSI compatible changed between patchset revisions, but that wasn't > reflected in the bindings. Fix it. > > 0eda3c6cb1c5 ("dt-bindings: display/msm: add support for the display on SM8450") > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.example.dtb: display-subsystem@ae00000: phy@ae94400:compatible:0: 'qcom,sm8450-dsi-phy-5nm' was expected From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.example.dtb: display-subsystem@ae00000: phy@ae96400:compatible:0: 'qcom,sm8450-dsi-phy-5nm' was expected From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.yaml Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.example.dtb: /example-0/display-subsystem@ae00000/phy@ae94400: failed to match any schema with compatible: ['qcom,dsi-phy-5nm-8450'] Documentation/devicetree/bindings/display/msm/qcom,sm8450-mdss.example.dtb: /example-0/display-subsystem@ae00000/phy@ae96400: failed to match any schema with compatible: ['qcom,dsi-phy-5nm-8450'] doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230323-topic-sm8450-upstream-dt-bindings-fixes-v1-1-3ead1e418fe4@linaro.org The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.