From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-renesas-soc@vger.kernel.org,
Gilad Ben-Yossef <gilad@benyossef.com>
Subject: Re: [PATCH] dt-bindings: crypto: ccree: Convert to json-schema
Date: Thu, 24 Jun 2021 15:13:48 -0600 [thread overview]
Message-ID: <20210624211348.GA1991366@robh.at.kernel.org> (raw)
In-Reply-To: <ab361a862755e281f5fef67b3f678d66ae201781.1623413974.git.geert+renesas@glider.be>
On Fri, 11 Jun 2021 14:20:17 +0200, Geert Uytterhoeven wrote:
> Convert the Arm TrustZone CryptoCell cryptographic engine Device Tree
> binding documentation to json-schema.
>
> Document missing properties.
> Update the example to match reality.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../bindings/crypto/arm,cryptocell.yaml | 53 +++++++++++++++++++
> .../bindings/crypto/arm-cryptocell.txt | 25 ---------
> 2 files changed, 53 insertions(+), 25 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/arm,cryptocell.yaml
> delete mode 100644 Documentation/devicetree/bindings/crypto/arm-cryptocell.txt
>
I'm applying this version which is dual licensed as that is the
preference of my employeer, Arm, who is the copyright holder here. I'll
sort this out internally with Gilad.
Besides, for the bulk of the new file Geert is the copyright holder.
Rob
next prev parent reply other threads:[~2021-06-24 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 12:20 [PATCH] dt-bindings: crypto: ccree: Convert to json-schema Geert Uytterhoeven
2021-06-14 8:12 ` Gilad Ben-Yossef
2021-06-24 21:13 ` Rob Herring [this message]
2021-06-25 9:05 ` Gilad Ben-Yossef
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=20210624211348.GA1991366@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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 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.