public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Roger Quadros <rogerq@kernel.org>
Cc: linux-kernel@vger.kernel.org, tony@atomide.com, nm@ti.com,
	lokeshvutla@ti.com, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml
Date: Thu, 26 Aug 2021 08:26:01 -0500	[thread overview]
Message-ID: <1629984361.367999.1033385.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210826085731.15300-1-rogerq@kernel.org>

On Thu, 26 Aug 2021 11:57:31 +0300, Roger Quadros wrote:
> Convert omap-gpmc.txt to ti,gpmc.yaml.
> 
> Signed-off-by: Roger Quadros <rogerq@kernel.org>
> ---
>  .../bindings/memory-controllers/omap-gpmc.txt | 157 --------
>  .../bindings/memory-controllers/ti,gpmc.yaml  | 360 ++++++++++++++++++
>  2 files changed, 360 insertions(+), 157 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
>  create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti,gpmc.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:
Documentation/devicetree/bindings/memory-controllers/ti,gpmc.example.dt.yaml:0:0: /example-0/memory-controller@50000000/nand-controller@0,0: failed to match any schema with compatible: ['ti,omap2-nand']

doc reference errors (make refcheckdocs):
Warning: Documentation/devicetree/bindings/mtd/gpmc-nand.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Warning: Documentation/devicetree/bindings/mtd/gpmc-nor.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Warning: Documentation/devicetree/bindings/mtd/gpmc-nor.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Warning: Documentation/devicetree/bindings/mtd/gpmc-onenand.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Warning: Documentation/devicetree/bindings/net/gpmc-eth.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Warning: Documentation/devicetree/bindings/net/gpmc-eth.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/mtd/gpmc-nand.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/mtd/gpmc-nor.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/mtd/gpmc-nor.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/mtd/gpmc-onenand.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/net/gpmc-eth.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
Documentation/devicetree/bindings/net/gpmc-eth.txt: Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt

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

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:[~2021-08-26 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  8:57 [PATCH] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml Roger Quadros
2021-08-26 13:26 ` 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=1629984361.367999.1033385.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.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