All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	linux-rpi-kernel@lists.infradead.org,
	"Matt Mackall" <mpm@selenic.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	linux-crypto@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	linux-kernel@vger.kernel.org,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Rikard Falkeborn" <rikard.falkeborn@gmail.com>,
	"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
	linux-arm-kernel@lists.infradead.org,
	"Scott Branden" <sbranden@broadcom.com>,
	"Mark Brown" <broonie@kernel.org>, "Ray Jui" <rjui@broadcom.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	devicetree@vger.kernel.org,
	"Stefan Wahren" <stefan.wahren@i2se.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: rng: bcm2835: document reset support
Date: Tue, 23 Feb 2021 13:34:10 -0600	[thread overview]
Message-ID: <1614108850.556529.4116106.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210223170006.29558-2-noltari@gmail.com>

On Tue, 23 Feb 2021 18:00:05 +0100, Álvaro Fernández Rojas wrote:
> Some devices may need to perform a reset before using the RNG, such as the
> BCM6368.
> 
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
>  v3: make resets required if brcm,bcm6368-rng.
>  v2: document reset support.
> 
>  .../devicetree/bindings/rng/brcm,bcm2835.yaml   | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:

dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/rng/brcm,bcm2835.example.dt.yaml: rng@10004180: 'resets' does not match any of the regexes: 'pinctrl-[0-9]+'
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml

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

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.


WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Scott Branden" <sbranden@broadcom.com>,
	"Ray Jui" <rjui@broadcom.com>, "Mark Brown" <broonie@kernel.org>,
	"Stefan Wahren" <stefan.wahren@i2se.com>,
	linux-kernel@vger.kernel.org,
	"Rikard Falkeborn" <rikard.falkeborn@gmail.com>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
	"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Matt Mackall" <mpm@selenic.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: rng: bcm2835: document reset support
Date: Tue, 23 Feb 2021 13:34:10 -0600	[thread overview]
Message-ID: <1614108850.556529.4116106.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210223170006.29558-2-noltari@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

On Tue, 23 Feb 2021 18:00:05 +0100, Álvaro Fernández Rojas wrote:
> Some devices may need to perform a reset before using the RNG, such as the
> BCM6368.
> 
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
>  v3: make resets required if brcm,bcm6368-rng.
>  v2: document reset support.
> 
>  .../devicetree/bindings/rng/brcm,bcm2835.yaml   | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:

dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/rng/brcm,bcm2835.example.dt.yaml: rng@10004180: 'resets' does not match any of the regexes: 'pinctrl-[0-9]+'
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml

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

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.



[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-23 19:35 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 19:45 [PATCH] hwrng: bcm2835: add reset support Álvaro Fernández Rojas
2021-02-22 19:45 ` Álvaro Fernández Rojas
2021-02-23 16:01 ` [PATCH 0/2] " Álvaro Fernández Rojas
2021-02-23 16:01   ` Álvaro Fernández Rojas
2021-02-23 16:01   ` [PATCH 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-23 16:01     ` Álvaro Fernández Rojas
2021-02-23 16:36     ` Florian Fainelli
2021-02-23 16:36       ` Florian Fainelli
2021-02-23 17:17       ` Scott Branden
2021-02-23 17:17         ` Scott Branden
2021-02-23 17:22         ` Álvaro Fernández Rojas
2021-02-23 17:22           ` Álvaro Fernández Rojas
2021-02-23 16:01   ` [PATCH 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-02-23 16:01     ` Álvaro Fernández Rojas
2021-02-24  8:22   ` [PATCH v4 0/2] " Álvaro Fernández Rojas
2021-02-24  8:22     ` Álvaro Fernández Rojas
2021-02-24  8:22     ` [PATCH v4 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-24  8:22       ` Álvaro Fernández Rojas
2021-02-24  8:22     ` [PATCH v4 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-02-24  8:22       ` Álvaro Fernández Rojas
2021-03-03 13:52       ` Philipp Zabel
2021-03-03 13:52         ` Philipp Zabel
2021-03-03 14:06         ` Álvaro Fernández Rojas
2021-03-03 14:06           ` Álvaro Fernández Rojas
2021-03-03 19:16           ` Florian Fainelli
2021-03-03 19:16             ` Florian Fainelli
2021-02-23 17:00 ` [PATCH v3 0/2] " Álvaro Fernández Rojas
2021-02-23 17:00   ` Álvaro Fernández Rojas
2021-02-23 17:00   ` [PATCH v3 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-23 17:00     ` Álvaro Fernández Rojas
2021-02-23 19:34     ` Rob Herring [this message]
2021-02-23 19:34       ` Rob Herring
2021-02-23 20:48       ` Álvaro Fernández Rojas
2021-02-23 20:48         ` Álvaro Fernández Rojas
2021-03-04 12:07     ` Nicolas Saenz Julienne
2021-03-04 12:07       ` Nicolas Saenz Julienne
2021-03-04 12:18       ` Álvaro Fernández Rojas
2021-03-04 12:18         ` Álvaro Fernández Rojas
2021-03-04 13:30         ` Nicolas Saenz Julienne
2021-03-04 13:30           ` Nicolas Saenz Julienne
2021-03-04 14:57           ` Álvaro Fernández Rojas
2021-03-04 14:57             ` Álvaro Fernández Rojas
2021-03-04 19:58       ` Rob Herring
2021-03-04 19:58         ` Rob Herring
2021-02-23 17:00   ` [PATCH v3 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-02-23 17:00     ` Álvaro Fernández Rojas
2021-02-23 20:43     ` Florian Fainelli
2021-02-23 20:43       ` Florian Fainelli

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=1614108850.556529.4116106.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=mpm@selenic.com \
    --cc=nfraprado@protonmail.com \
    --cc=noltari@gmail.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=p.zabel@pengutronix.de \
    --cc=rikard.falkeborn@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.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 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.