From: Fabio Estevam <festevam@gmail.com>
To: herbert@gondor.apana.org.au
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH 2/4] dt-bindings: crypto: fsl-imx-sahara: Remove leading space
Date: Sun, 24 Sep 2023 19:31:02 -0300 [thread overview]
Message-ID: <20230924223104.862169-2-festevam@gmail.com> (raw)
In-Reply-To: <20230924223104.862169-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
Remove the leading space in the reg property as this is the standard.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml b/Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml
index c7da09c58eff..bad82491cd6a 100644
--- a/Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml
+++ b/Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml
@@ -32,6 +32,6 @@ examples:
- |
crypto@10025000 {
compatible = "fsl,imx27-sahara";
- reg = < 0x10025000 0x800>;
+ reg = <0x10025000 0x800>;
interrupts = <75>;
};
--
2.34.1
next prev parent reply other threads:[~2023-09-24 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 22:31 [PATCH 1/4] dt-bindings: crypto: fsl-imx-sahara: Shorten the title Fabio Estevam
2023-09-24 22:31 ` Fabio Estevam [this message]
2023-09-25 6:55 ` [PATCH 2/4] dt-bindings: crypto: fsl-imx-sahara: Remove leading space Krzysztof Kozlowski
2023-09-24 22:31 ` [PATCH 3/4] dt-bindings: crypto: fsl-imx-sahara: Document the clocks Fabio Estevam
2023-09-25 6:56 ` Krzysztof Kozlowski
2023-09-24 22:31 ` [PATCH 4/4] dt-bindings: crypto: fsl-imx-sahara: Fix the number of irqs Fabio Estevam
2023-09-25 6:56 ` Krzysztof Kozlowski
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=20230924223104.862169-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-crypto@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 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).