From: Rob Herring <robh@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: sre@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Dan Murphy <dmurphy@ti.com>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] dt-bindings: power: Convert power_supply text to yaml
Date: Fri, 1 May 2020 16:13:51 -0500 [thread overview]
Message-ID: <20200501211351.GA4774@bogus> (raw)
In-Reply-To: <20200430151841.17453-1-dmurphy@ti.com>
On Thu, 30 Apr 2020 10:18:41 -0500, Dan Murphy wrote:
> Convert the power_supply.txt to power-supply.yaml.
> This conversion entailed fixing up the binding to being yaml and dt
> checker compliant.
>
> Added a note in the power_supply.txt to reference the power-supply.yaml
>
> CC: Rob Herring <robh@kernel.org>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
> .../bindings/power/supply/power-supply.yaml | 40 +++++++++++++++++++
> .../bindings/power/supply/power_supply.txt | 25 +-----------
> 2 files changed, 42 insertions(+), 23 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/power/supply/power-supply.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/power/supply/power-supply.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/power/supply/power-supply.yaml#
See https://patchwork.ozlabs.org/patch/1280522
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.
prev parent reply other threads:[~2020-05-01 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 15:18 [PATCH] dt-bindings: power: Convert power_supply text to yaml Dan Murphy
2020-05-01 16:58 ` Sebastian Reichel
2020-05-01 17:00 ` Dan Murphy
2020-05-01 21:13 ` Rob Herring [this message]
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=20200501211351.GA4774@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.