From: Ricardo Rivera-Matos <r-rivera-matos@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: <pali@kernel.org>, <linux-pm@vger.kernel.org>,
<sspatil@android.com>, <linux-kernel@vger.kernel.org>,
<afd@ti.com>, <dmurphy@ti.com>, <sre@kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH v15 2/4] dt-bindings: power: Convert battery.txt to battery.yaml
Date: Mon, 6 Jul 2020 13:45:24 -0500 [thread overview]
Message-ID: <54914eed-4a65-745b-b61b-9515737023e3@ti.com> (raw)
In-Reply-To: <20200702205320.GA1672139@bogus>
Rob
On 7/2/20 3:53 PM, Rob Herring wrote:
> On Wed, 01 Jul 2020 16:10:42 -0500, Ricardo Rivera-Matos wrote:
>> From: Dan Murphy <dmurphy@ti.com>
>>
>> Convert the battery.txt file to yaml and fix up the examples.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>> .../bindings/power/supply/battery.txt | 86 +---------
>> .../bindings/power/supply/battery.yaml | 157 ++++++++++++++++++
>> 2 files changed, 158 insertions(+), 85 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/power/supply/battery.yaml
>>
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> Unknown file referenced: [Errno 2] No such file or directory: '/usr/local/lib/python3.6/dist-packages/dtschema/schema/types.yaml'
> Documentation/devicetree/bindings/Makefile:20: recipe for target 'Documentation/devicetree/bindings/power/supply/battery.example.dts' failed
> make[1]: *** [Documentation/devicetree/bindings/power/supply/battery.example.dts] Error 255
> make[1]: *** Waiting for unfinished jobs....
> Makefile:1347: recipe for target 'dt_binding_check' failed
> make: *** [dt_binding_check] Error 2
I think your bot is looking for the types.yaml in the wrong place.
'/usr/local/lib/python3.6/dist-packages/dtschema/schema/types.yaml'
should be
'/usr/local/lib/python3.6/dist-packages/dtschema/schemas/types.yaml'. I
renamed might 'schemas' directory to 'schema' and my battery.yaml passed
the dt_binding_check.
>
>
> See https://patchwork.ozlabs.org/patch/1320813
>
> 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
Confirmed on latest dt-schema
>
> Please check and re-submit.
Thanks,
Ricardo
>
next prev parent reply other threads:[~2020-07-06 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 21:10 [PATCH v15 0/4] Add JEITA properties and introduce the bq2515x charger Ricardo Rivera-Matos
2020-07-01 21:10 ` [PATCH v15 1/4] power_supply: Add additional health properties to the header Ricardo Rivera-Matos
2020-07-01 21:10 ` [PATCH v15 2/4] dt-bindings: power: Convert battery.txt to battery.yaml Ricardo Rivera-Matos
2020-07-02 20:53 ` Rob Herring
2020-07-06 18:45 ` Ricardo Rivera-Matos [this message]
2020-07-07 14:40 ` [EXTERNAL] " Rob Herring
2020-07-07 18:07 ` Ricardo Rivera-Matos
2020-07-01 21:10 ` [PATCH v15 3/4] dt-bindings: power: Add the bindings for the bq2515x family of chargers Ricardo Rivera-Matos
2020-07-01 21:10 ` [PATCH v15 4/4] power: supply: bq25150 introduce the bq25150 Ricardo Rivera-Matos
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=54914eed-4a65-745b-b61b-9515737023e3@ti.com \
--to=r-rivera-matos@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=sspatil@android.com \
/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).