From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
UNGLinuxDriver@microchip.com, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: dts: add missing space before {
Date: Thu, 6 Jul 2023 14:47:58 +0200 [thread overview]
Message-ID: <ZKa3/r1GtOW36aoW@alpha.franken.de> (raw)
In-Reply-To: <20230705145724.292793-1-krzysztof.kozlowski@linaro.org>
On Wed, Jul 05, 2023 at 04:57:24PM +0200, Krzysztof Kozlowski wrote:
> Add missing whitespace between node name/label and opening {.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> arch/mips/boot/dts/mscc/serval_common.dtsi | 2 +-
> arch/mips/boot/dts/pic32/pic32mzda.dtsi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/boot/dts/mscc/serval_common.dtsi b/arch/mips/boot/dts/mscc/serval_common.dtsi
> index 0893de420e27..5dc1eac49e50 100644
> --- a/arch/mips/boot/dts/mscc/serval_common.dtsi
> +++ b/arch/mips/boot/dts/mscc/serval_common.dtsi
> @@ -20,7 +20,7 @@ chosen {
> stdout-path = "serial0:115200n8";
> };
>
> - i2c0_imux: i2c0-imux{
> + i2c0_imux: i2c0-imux {
> compatible = "i2c-mux-pinctrl";
> #address-cells = <1>;
> #size-cells = <0>;
> diff --git a/arch/mips/boot/dts/pic32/pic32mzda.dtsi b/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> index f1e3dad6bead..fdc721b414a8 100644
> --- a/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> +++ b/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> @@ -75,7 +75,7 @@ evic: interrupt-controller@1f810000 {
> microchip,external-irqs = <3 8 13 18 23>;
> };
>
> - pic32_pinctrl: pinctrl@1f801400{
> + pic32_pinctrl: pinctrl@1f801400 {
> #address-cells = <1>;
> #size-cells = <1>;
> compatible = "microchip,pic32mzda-pinctrl";
> --
> 2.34.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-07-06 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:57 Krzysztof Kozlowski
2023-07-06 12:47 ` Thomas Bogendoerfer [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=ZKa3/r1GtOW36aoW@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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
all inboxes | Powered by JetHome®