From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: mark.rutland@arm.com, lionel.debieve@st.com,
alexandre.torgue@st.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, robh+dt@kernel.org,
linux-crypto@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH] dt-bindings: crypto: Convert stm32 CRC bindings to json-schema
Date: Thu, 14 Nov 2019 12:27:41 -0600 [thread overview]
Message-ID: <20191114182741.GA28603@bogus> (raw)
In-Reply-To: <20191108125244.23001-1-benjamin.gaignard@st.com>
On Fri, 8 Nov 2019 13:52:42 +0100, Benjamin Gaignard wrote:
> Convert the STM32 CRC binding to DT schema format using json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> .../devicetree/bindings/crypto/st,stm32-crc.txt | 16 ---------
> .../devicetree/bindings/crypto/st,stm32-crc.yaml | 38 ++++++++++++++++++++++
> 2 files changed, 38 insertions(+), 16 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-crc.txt
> create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-crc.yaml
>
Applied, thanks.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-14 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 12:52 [PATCH] dt-bindings: crypto: Convert stm32 CRC bindings to json-schema Benjamin Gaignard
2019-11-08 12:52 ` [PATCH] dt-bindings: crypto: Convert stm32 CRYP " Benjamin Gaignard
2019-11-14 18:28 ` Rob Herring
2019-11-08 12:52 ` [PATCH] dt-bindings: crypto: Convert stm32 HASH " Benjamin Gaignard
2019-11-14 18:27 ` Rob Herring
2019-11-14 18:27 ` 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=20191114182741.GA28603@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--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-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@st.com \
--cc=mark.rutland@arm.com \
--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 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).