Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1638453489.532760.3736891.nullmailer@robh.at.kernel.org>
References: <1638403212-29265-1-git-send-email-quic_fenglinw@quicinc.com> <1638403212-29265-11-git-send-email-quic_fenglinw@quicinc.com> <1638453489.532760.3736891.nullmailer@robh.at.kernel.org>
Subject: Re: [RESEND PATCH v3 10/10] dt-bindings: convert qcom,spmi-pmic-arb binding to YAML format
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     linux-kernel@vger.kernel.org,
        Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>,
        collinsd@codeaurora.org, Andy Gross <agross@kernel.org>,
        devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
        subbaram@codeaurora.org, tglx@linutronix.de, maz@kernel.org,
        Rob Herring <robh+dt@kernel.org>,
        Bjorn Andersson <bjorn.andersson@linaro.org>
To:     Fenglin Wu <quic_fenglinw@quicinc.com>,
        Rob Herring <robh@kernel.org>
Date:   Thu, 09 Dec 2021 18:05:48 -0800
User-Agent: alot/0.9.1
Message-Id: <20211210020549.BFA4DC004DD@smtp.kernel.org>
Precedence: bulk

Quoting Rob Herring (2021-12-02 05:58:09)
> On Thu, 02 Dec 2021 08:00:12 +0800, Fenglin Wu wrote:
> > Convert the SPMI PMIC arbiter documentation to JSON/yaml. While at it,
> > update SPMI bus "reg" items constraint for SPMI PMIC arbiter to carry
> > it and update it with a smaller range.
> >=20
> > Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com>
> > ---
> >  .../bindings/spmi/qcom,spmi-pmic-arb.txt           |  67 -----------
> >  .../bindings/spmi/qcom,spmi-pmic-arb.yaml          | 128 +++++++++++++=
++++++++
> >  Documentation/devicetree/bindings/spmi/spmi.yaml   |   3 +-
> >  3 files changed, 130 insertions(+), 68 deletions(-)
> >  delete mode 100644 Documentation/devicetree/bindings/spmi/qcom,spmi-pm=
ic-arb.txt
> >  create mode 100644 Documentation/devicetree/bindings/spmi/qcom,spmi-pm=
ic-arb.yaml
> >=20
>=20
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>=20
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
>=20
> Full log is available here: https://patchwork.ozlabs.org/patch/1562483

Are any of these problems going to be fixed?