From: Troy Mitchell <troymitchell988@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@gentoo.org>,
Troy Mitchell <troymitchell988@gmail.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: spacemit,k1-i2c: Minor whitespace cleanup in example
Date: Fri, 22 Aug 2025 09:32:15 +0800 [thread overview]
Message-ID: <aKfInxTH8XeZo55z@troy-wujie14pro-arch> (raw)
In-Reply-To: <20250821083205.46600-2-krzysztof.kozlowski@linaro.org>
On Thu, Aug 21, 2025 at 10:32:06AM +0200, Krzysztof Kozlowski wrote:
> The DTS code coding style expects exactly one space around '='
> character.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml b/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml
> index 3d6aefb0d0f1..c1a3004df71d 100644
> --- a/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml
> @@ -53,7 +53,7 @@ examples:
> reg = <0xd4010800 0x38>;
> interrupt-parent = <&plic>;
> interrupts = <36>;
> - clocks =<&ccu 32>, <&ccu 84>;
> + clocks = <&ccu 32>, <&ccu 84>;
Reviewed-by: Troy Mitchell <troymitchell988@gmail.com>
Best regards,
Troy
> clock-names = "func", "bus";
> clock-frequency = <100000>;
> };
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-08-22 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:32 [PATCH] dt-bindings: i2c: spacemit,k1-i2c: Minor whitespace cleanup in example Krzysztof Kozlowski
2025-08-22 1:32 ` Troy Mitchell [this message]
2025-08-22 19:29 ` Rob Herring (Arm)
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=aKfInxTH8XeZo55z@troy-wujie14pro-arch \
--to=troymitchell988@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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).