From: Rob Herring <robh@kernel.org>
To: Caleb Connolly <caleb@connolly.tech>
Cc: linux-input@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Joel Selvaraj <jo@jsfamily.in>,
linux-kernel@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jami Kettunen <jami.kettunen@somainline.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: input: add Qualcomm SPMI haptics driver
Date: Tue, 17 Aug 2021 07:10:48 -0500 [thread overview]
Message-ID: <1629202248.430426.4133262.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210816221931.1998187-2-caleb@connolly.tech>
On Mon, 16 Aug 2021 22:19:55 +0000, Caleb Connolly wrote:
> Add bindings for qcom PMIC SPMI haptics driver.
>
> Signed-off-by: Caleb Connolly <caleb@connolly.tech>
> ---
> .../bindings/input/qcom,spmi-haptics.yaml | 128 ++++++++++++++++++
> include/dt-bindings/input/qcom,spmi-haptics.h | 32 +++++
> 2 files changed, 160 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/qcom,spmi-haptics.yaml
> create mode 100644 include/dt-bindings/input/qcom,spmi-haptics.h
>
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:
Documentation/devicetree/bindings/input/qcom,spmi-haptics.example.dt.yaml:0:0: /example-0/pmic@3: failed to match any schema with compatible: ['qcom,pmi8998', 'qcom,spmi-pmic']
Documentation/devicetree/bindings/input/qcom,spmi-haptics.example.dt.yaml:0:0: /example-0/pmic@3: failed to match any schema with compatible: ['qcom,pmi8998', 'qcom,spmi-pmic']
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1517351
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
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.
next prev parent reply other threads:[~2021-08-17 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 22:19 [PATCH v3 0/6] input: Introduce support for SPMI haptics found on Qcom PMICs Caleb Connolly
2021-08-16 22:19 ` [PATCH v3 1/6] dt-bindings: input: add Qualcomm SPMI haptics driver Caleb Connolly
2021-08-17 12:10 ` Rob Herring [this message]
2021-08-16 22:20 ` [PATCH v3 2/6] " Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 3/6] arm64: dts: qcom: pmi8998: introduce spmi haptics Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 4/6] arm64: dts: qcom: sdm845-oneplus-common: add haptics Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 5/6] arm64: dts: qcom: sdm845-xiaomi-beryllium: " Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 6/6] arm64: dts: qcom: msm8998-oneplus-common: Enable PMI8998 haptics Caleb Connolly
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=1629202248.430426.4133262.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jami.kettunen@somainline.org \
--cc=jo@jsfamily.in \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).