From: "Heiko Stübner" <heiko@sntech.de>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
krzysztof.kozlowski@canonical.com, robh+dt@kernel.org,
Corentin Labbe <clabbe@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH] dt-bindings: crypto: rockchip: fix a typo on crypto-controller
Date: Wed, 09 Feb 2022 11:19:54 +0100 [thread overview]
Message-ID: <4940101.4UnPYNKMnq@diego> (raw)
In-Reply-To: <20220209101721.1659574-1-clabbe@baylibre.com>
Hi Corentin,
Am Mittwoch, 9. Februar 2022, 11:17:21 CET schrieb Corentin Labbe:
> crypto-controller had a typo, fix it.
>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
the binding for the crypto-accelerator is pretty standard
without any crazy stuff, so you could also try to convert it
to the yaml format ;-)
Heiko
> ---
> Documentation/devicetree/bindings/crypto/rockchip-crypto.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt b/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt
> index 5e2ba385b8c9..53e39d5f94e7 100644
> --- a/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt
> +++ b/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt
> @@ -16,7 +16,7 @@ Required properties:
>
> Examples:
>
> - crypto: cypto-controller@ff8a0000 {
> + crypto: crypto-controller@ff8a0000 {
> compatible = "rockchip,rk3288-crypto";
> reg = <0xff8a0000 0x4000>;
> interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>;
>
prev parent reply other threads:[~2022-02-09 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:17 [PATCH] dt-bindings: crypto: rockchip: fix a typo on crypto-controller Corentin Labbe
2022-02-09 10:19 ` Heiko Stübner [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=4940101.4UnPYNKMnq@diego \
--to=heiko@sntech.de \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 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).