linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
	devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: Document RZ/V2M I2C controller
Date: Tue, 28 Jun 2022 20:09:39 -0600	[thread overview]
Message-ID: <1656468579.925440.1403681.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220628194526.111501-2-phil.edworthy@renesas.com>

On Tue, 28 Jun 2022 20:45:25 +0100, Phil Edworthy wrote:
> Document Renesas RZ/V2M (r9a09g011) I2C controller bindings.
> 
> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
> Reviewed-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v2:
>  - Use an enum and set the default for clock-frequency
>  - Add resets property
> ---
>  .../bindings/i2c/renesas,rzv2m.yaml           | 80 +++++++++++++++++++
>  1 file changed, 80 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/i2c/renesas,rzv2m.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/iio/temperature/adi,ltc2983.yaml: patternProperties:^thermistor@:properties:adi,excitation-current-nanoamp: '$ref' should not be valid under {'const': '$ref'}
	hint: Standard unit suffix properties don't need a type $ref
	from schema $id: http://devicetree.org/meta-schemas/core.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml: ignoring, error in schema: patternProperties: ^thermistor@: properties: adi,excitation-current-nanoamp
Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.example.dtb:0:0: /example-0/spi/ltc2983@0: failed to match any schema with compatible: ['adi,ltc2983']

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/patch/

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.


  reply	other threads:[~2022-06-29  2:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 19:45 [PATCH v2 0/2] i2c: Add new driver for Renesas RZ/V2M controller Phil Edworthy
2022-06-28 19:45 ` [PATCH v2 1/2] dt-bindings: i2c: Document RZ/V2M I2C controller Phil Edworthy
2022-06-29  2:09   ` Rob Herring [this message]
2022-06-29  6:53     ` Geert Uytterhoeven
2022-06-29  8:15       ` Krzysztof Kozlowski
2022-06-29 13:50         ` Rob Herring
2022-06-29  8:22   ` Krzysztof Kozlowski
2022-06-30 11:43     ` Phil Edworthy
2022-06-28 19:45 ` [PATCH v2 2/2] i2c: Add Renesas RZ/V2M controller Phil Edworthy
2022-06-28 21:08   ` Andy Shevchenko
2022-06-29  6:52     ` Geert Uytterhoeven
2022-06-29 10:43       ` Andy Shevchenko
2022-06-29 15:58         ` Geert Uytterhoeven
2022-06-29 16:10           ` Andy Shevchenko
2022-06-30  9:41     ` Phil Edworthy
2022-06-30  9:54       ` Andy Shevchenko
2022-06-29 16:26   ` Philipp Zabel
2022-06-29 16:20 ` [PATCH v2 0/2] i2c: Add new driver for " Philipp Zabel
2022-06-29 17:18   ` Geert Uytterhoeven
2022-06-30 13:43     ` Phil Edworthy
2022-06-30 14:45       ` Philipp Zabel
2022-06-30 15:16         ` Phil Edworthy
2022-07-01 15:40           ` Philipp Zabel
2022-07-01 16:18             ` Phil Edworthy
2022-07-01 15:40     ` Philipp Zabel

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=1656468579.925440.1403681.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=phil.edworthy@renesas.com \
    --cc=robh+dt@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 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).