From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Vladimir Zapolskiy <vz@mleia.com>,
Kamil Konieczny <k.konieczny@partner.samsung.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: crypto: samsung: Convert SSS and SlimSSS bindings to json-schema
Date: Thu, 10 Oct 2019 16:25:25 -0500 [thread overview]
Message-ID: <20191010212525.GA10949@bogus> (raw)
In-Reply-To: <20190920163635.9186-1-krzk@kernel.org>
On Fri, 20 Sep 2019 18:36:35 +0200, Krzysztof Kozlowski wrote:
> Convert Samsung Exynos Security SubSystem (SSS) and SlimSSS hardware
> crypto accelerator bindings to DT schema format using json-schema.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> ---
>
> Rebased on linux-next due to conflicting change in MAINTAINERS file
> coming through arm-soc tree.
>
> Changes since v1:
> 1. Add additionalProperties:false
> ---
> .../bindings/crypto/samsung-slimsss.txt | 19 ------
> .../bindings/crypto/samsung-slimsss.yaml | 47 +++++++++++++++
> .../bindings/crypto/samsung-sss.txt | 32 ----------
> .../bindings/crypto/samsung-sss.yaml | 58 +++++++++++++++++++
> MAINTAINERS | 4 +-
> 5 files changed, 107 insertions(+), 53 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/crypto/samsung-slimsss.txt
> create mode 100644 Documentation/devicetree/bindings/crypto/samsung-slimsss.yaml
> delete mode 100644 Documentation/devicetree/bindings/crypto/samsung-sss.txt
> create mode 100644 Documentation/devicetree/bindings/crypto/samsung-sss.yaml
>
Applied, thanks.
Rob
prev parent reply other threads:[~2019-10-10 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:36 [PATCH v2] dt-bindings: crypto: samsung: Convert SSS and SlimSSS bindings to json-schema Krzysztof Kozlowski
2019-10-10 21:25 ` 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=20191010212525.GA10949@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=k.konieczny@partner.samsung.com \
--cc=krzk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=vz@mleia.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.