From: Rob Herring <robh@kernel.org>
To: Ravi Kumar Bokka <rbokka@codeaurora.org>
Cc: rnayak@codeaurora.org, Rob Herring <robh+dt@kernel.org>,
saiprakash.ranjan@codeaurora.org, sparate@codeaurora.org,
mturney@codeaurora.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
mkurumel@codeaurora.org, linux-kernel@vger.kernel.org,
dhavalp@codeaurora.org, c_rbokka@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [RFC v1 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse
Date: Tue, 12 May 2020 17:36:35 -0500 [thread overview]
Message-ID: <20200512223635.GA29448@bogus> (raw)
In-Reply-To: <1589307480-27508-2-git-send-email-rbokka@codeaurora.org>
On Tue, 12 May 2020 23:47:58 +0530, Ravi Kumar Bokka wrote:
> This patch adds dt-bindings document for qfprom-efuse controller.
>
> Signed-off-by: Ravi Kumar Bokka <rbokka@codeaurora.org>
> ---
> .../devicetree/bindings/nvmem/qfprom-efuse.yaml | 40 ++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml: while scanning a block scalar
in "<unicode string>", line 30, column 5
found a tab character where an indentation space is expected
in "<unicode string>", line 34, column 1
Documentation/devicetree/bindings/Makefile:12: recipe for target 'Documentation/devicetree/bindings/nvmem/qfprom-efuse.example.dts' failed
make[1]: *** [Documentation/devicetree/bindings/nvmem/qfprom-efuse.example.dts] Error 1
make[1]: *** Waiting for unfinished jobs....
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml: ignoring, error parsing file
warning: no schema found in file: ./Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml: ignoring, error parsing file
warning: no schema found in file: ./Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml
Makefile:1300: recipe for target 'dt_binding_check' failed
make: *** [dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1288685
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:
pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-05-12 22:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 18:17 [RFC v1 0/3] Add QTI QFPROM-Efuse driver support Ravi Kumar Bokka
2020-05-12 18:17 ` [RFC v1 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse Ravi Kumar Bokka
2020-05-12 22:36 ` Rob Herring [this message]
2020-05-12 23:03 ` Doug Anderson
2020-05-12 18:17 ` [RFC v1 2/3] drivers: nvmem: Add driver for QTI qfprom-efuse support Ravi Kumar Bokka
2020-05-12 19:20 ` Randy Dunlap
2020-05-12 23:02 ` Doug Anderson
2020-05-13 13:20 ` Srinivas Kandagatla
2020-05-14 12:26 ` Ravi Kumar Bokka (Temp)
2020-05-14 18:21 ` Doug Anderson
2020-05-17 14:57 ` Ravi Kumar Bokka (Temp)
2020-05-18 10:33 ` Ravi Kumar Bokka (Temp)
2020-05-15 11:09 ` Srinivas Kandagatla
2020-05-18 10:39 ` Ravi Kumar Bokka (Temp)
2020-05-18 10:44 ` Srinivas Kandagatla
2020-05-18 18:31 ` Doug Anderson
2020-05-20 14:35 ` Srinivas Kandagatla
2020-05-20 22:48 ` Doug Anderson
2020-05-21 15:00 ` Srinivas Kandagatla
2020-05-21 15:10 ` Doug Anderson
2020-05-21 15:55 ` Srinivas Kandagatla
2020-05-21 21:28 ` Doug Anderson
2020-05-22 11:18 ` Srinivas Kandagatla
2020-05-26 22:31 ` Doug Anderson
2020-06-01 9:24 ` Srinivas Kandagatla
2020-06-01 18:08 ` Doug Anderson
2020-06-02 10:56 ` Srinivas Kandagatla
2020-05-12 18:18 ` [RFC v1 3/3] arm64: dts: qcom: sc7180: Add qfprom-efuse Ravi Kumar Bokka
2020-05-12 23:03 ` [RFC v1 0/3] Add QTI QFPROM-Efuse driver support Doug Anderson
[not found] ` <fb7f601f-388f-8a77-bb22-e1398f90326f@codeaurora.org>
2020-05-14 18:21 ` Doug Anderson
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=20200512223635.GA29448@bogus \
--to=robh@kernel.org \
--cc=c_rbokka@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dhavalp@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkurumel@codeaurora.org \
--cc=mturney@codeaurora.org \
--cc=rbokka@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=sparate@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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).