devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: martin.petersen@oracle.com, avri.altman@wdc.com,
	alim.akhtar@samsung.com, linux-scsi@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	jejb@linux.ibm.com
Subject: Re: [PATCH 1/7] dt-bindings: ufs: Document Renesas R-Car UFS host controller
Date: Tue, 12 Apr 2022 10:18:47 -0500	[thread overview]
Message-ID: <1649776727.144250.224540.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220412073647.3808493-2-yoshihiro.shimoda.uh@renesas.com>

On Tue, 12 Apr 2022 16:36:41 +0900, Yoshihiro Shimoda wrote:
> Document Renesas R-Car UFS host controller for R-Car S4-8 (r8a779f0).
> 
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
>  .../devicetree/bindings/ufs/renesas,ufs.yaml  | 63 +++++++++++++++++++
>  1 file changed, 63 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/ufs/renesas,ufs.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/ufs/renesas,ufs.yaml: properties:clock-names: {'maxItems': 2, 'items': [{'const': 'fck'}, {'const': 'ref_clk'}]} should not be valid under {'required': ['maxItems']}
	hint: "maxItems" is not needed with an "items" list
	from schema $id: http://devicetree.org/meta-schemas/items.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/ufs/renesas,ufs.yaml: ignoring, error in schema: properties: clock-names
Documentation/devicetree/bindings/ufs/renesas,ufs.example.dtb:0:0: /example-0/scsi@e686000: failed to match any schema with compatible: ['renesas,r8a779f0-ufs']

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.


  parent reply	other threads:[~2022-04-12 15:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  7:36 [PATCH 0/7] treewide: scsi: ufs: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 1/7] dt-bindings: ufs: Document Renesas R-Car UFS host controller Yoshihiro Shimoda
2022-04-12 12:23   ` Krzysztof Kozlowski
2022-04-13  0:59     ` Yoshihiro Shimoda
2022-04-12 15:18   ` Rob Herring [this message]
2022-04-12  7:36 ` [PATCH 2/7] ufs: add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS Yoshihiro Shimoda
2022-04-15  6:45   ` Christoph Hellwig
2022-04-15  7:45     ` Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 3/7] ufs: add UFSHCD_QUIRK_HIBERN_FASTAUTO Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 4/7] scsi: ufs-renesas: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-04-12 12:24   ` Krzysztof Kozlowski
2022-04-13  1:24     ` Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 5/7] scsi: MAINTAINERS: Add maintainer for Renesas UFS driver Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 6/7] arm64: dts: renesas: r8a779f0: Add UFS node Yoshihiro Shimoda
2022-04-12  9:04   ` Krzysztof Kozlowski
2022-04-13  0:09     ` Yoshihiro Shimoda
2022-04-13  6:27       ` Krzysztof Kozlowski
2022-04-14  2:25         ` Yoshihiro Shimoda
2022-04-12  7:36 ` [PATCH 7/7] arm64: dts: renesas: r8a779f0: spider-cpu: Enable UFS device Yoshihiro Shimoda
2022-04-12  9:19 ` [PATCH 0/7] treewide: scsi: ufs: Add support for Renesas R-Car UFS controller Krzysztof Kozlowski
2022-04-12 15:52   ` Randy Dunlap

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=1649776727.144250.224540.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=robh+dt@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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).