From: Rob Herring <robh@kernel.org>
To: Marcello Sylvester Bauer <sylv@sylv.io>
Cc: Rob Herring <robh+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] dt-bindings: hwmon/pmbus: Add vicor,bcm6123 Bus Converter
Date: Mon, 17 Jan 2022 19:32:47 -0600 [thread overview]
Message-ID: <1642469567.779234.545737.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <ba6346942dfed14440e0243a6da510581389fbdd.1642434222.git.sylv@sylv.io>
On Mon, 17 Jan 2022 17:12:48 +0100, Marcello Sylvester Bauer wrote:
> Add bindings for BCM6123 Bus Converter from Vicor Corporation.
>
> Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io>
> ---
> .../bindings/hwmon/pmbus/vicor,bcm6123.yaml | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/vicor,bcm6123.yaml
>
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:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/hwmon/pmbus/vicor,bcm6123.yaml: 'maintainers' is a required property
hint: Metaschema for devicetree binding documentation
from schema $id: http://devicetree.org/meta-schemas/base.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/hwmon/pmbus/vicor,bcm6123.yaml: ignoring, error in schema:
Documentation/devicetree/bindings/hwmon/pmbus/vicor,bcm6123.example.dt.yaml:0:0: /example-0/i2c/bcm6123@5f: failed to match any schema with compatible: ['vicor,bcm6123']
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1580909
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:[~2022-01-18 1:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 16:12 [PATCH v1 0/4] Support bcm6123 Bus Converter Marcello Sylvester Bauer
2022-01-17 16:12 ` [PATCH v1 1/4] dt-bindings: vendor-prefixes: add Vicor Corporation Marcello Sylvester Bauer
2022-02-09 2:50 ` Rob Herring
2022-02-09 9:17 ` sylv
2022-01-17 16:12 ` [PATCH v1 2/4] dt-bindings: hwmon/pmbus: Add vicor,bcm6123 Bus Converter Marcello Sylvester Bauer
2022-01-17 17:06 ` Guenter Roeck
2022-01-18 7:48 ` sylv
2022-01-18 1:32 ` Rob Herring [this message]
2022-01-17 16:12 ` [PATCH v1 3/4] pmbus: remove trailing whitespaces Marcello Sylvester Bauer
2022-01-18 15:58 ` Guenter Roeck
2022-01-17 16:12 ` [PATCH v1 4/4] pmbus: Add support for bcm6123 Bus Converter Marcello Sylvester Bauer
2022-01-17 17:01 ` Guenter Roeck
2022-01-17 17:21 ` Guenter Roeck
2022-01-18 16:47 ` sylv
2022-01-18 17:51 ` Guenter Roeck
2022-02-09 9:22 ` [PATCH v1 0/4] Support " sylv
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=1642469567.779234.545737.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=sylv@sylv.io \
/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).