linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	davem@davemloft.net, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: crypto: sa2ul: fix a DT binding check warning
Date: Tue, 8 Sep 2020 16:45:01 -0600	[thread overview]
Message-ID: <20200908224501.GA1075868@bogus> (raw)
In-Reply-To: <20200825133106.21542-2-t-kristo@ti.com>

On Tue, 25 Aug 2020 16:31:05 +0300, Tero Kristo wrote:
> DT binding check produces a warning about bad cell size:
> 
> Documentation/devicetree/bindings/crypto/ti,sa2ul.example.dt.yaml: example-0: crypto@4e00000:reg:0: [0, 81788928, 0, 4608] is too long
> 	From schema: python3.6/site-packages/dtschema/schemas/reg.yaml
> 
> Fix this by reducing the address sizes for the example to 1 cell from
> current 2.
> 
> Fixes: 2ce9a7299bf6 ("dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation")
> Reported-by: Rob Herring <robh@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
>  Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied, thanks!

  reply	other threads:[~2020-09-08 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 13:31 [PATCH 0/2] crypto: sa2ul: couple of fixes Tero Kristo
2020-08-25 13:31 ` [PATCH 1/2] dt-bindings: crypto: sa2ul: fix a DT binding check warning Tero Kristo
2020-09-08 22:45   ` Rob Herring [this message]
2020-08-25 13:31 ` [PATCH 2/2] crypto: sa2ul: fix compiler warning produced by clang Tero Kristo
2020-08-26  5:23   ` Nathan Chancellor
2020-09-11  6:55   ` Herbert Xu

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=20200908224501.GA1075868@bogus \
    --to=robh@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=t-kristo@ti.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).