public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Heiko Stuebner" <heiko@sntech.de>, "Alexey Charkov" <alchark@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>,
	"Detlev Casanova" <detlev.casanova@collabora.com>,
	<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-rockchip@lists.infradead.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/4] arm64: dts: rockchip: enable further peripherals on ArmSoM Sige5
Date: Fri, 20 Jun 2025 12:10:10 +0200	[thread overview]
Message-ID: <DARA1V0ITPV5.T24DK4TVI0W7@cknow.org> (raw)
In-Reply-To: <5004008.8F6SAcFxjW@phil>


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

On Fri Jun 20, 2025 at 10:44 AM CEST, Heiko Stuebner wrote:
> Am Freitag, 20. Juni 2025, 10:40:49 Mitteleuropäische Sommerzeit schrieb Alexey Charkov:
>> On Fri, Jun 20, 2025 at 1:17 AM Heiko Stuebner <heiko@sntech.de> wrote:
>> >
>> > I've also fixed the wifi@1 node in the overlay - which was using
>> > spaces instead of tabs.
>> 
>> Thanks Heiko! It's annoying that YAML doesn't like tabs, so copying
>> from binding examples is not a universally good idea :)
>> 
>> By the way, is there any tool that helps catch those?
>
> checkpatch.pl would be the tool to do that, but I'm not sure it handles
> this at this time.
>
> I also only saw things when I looked at the patch in "mcedit", because
> it nicely distinguishes between tabs and spaces :-) .

In vim, ``:set list`` makes them visible as well.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

      reply	other threads:[~2025-06-20 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14 18:14 [PATCH v2 0/4] arm64: dts: rockchip: enable further peripherals on ArmSoM Sige5 Alexey Charkov
2025-06-14 18:14 ` [PATCH v2 1/4] arm64: dts: rockchip: list all CPU supplies " Alexey Charkov
2025-06-14 18:14 ` [PATCH v2 2/4] arm64: dts: rockchip: add SDIO controller on RK3576 Alexey Charkov
2025-06-14 18:14 ` [PATCH v2 3/4] arm64: dts: rockchip: add version-independent WiFi/BT nodes on Sige5 Alexey Charkov
2025-06-14 18:14 ` [PATCH v2 4/4] arm64: dts: rockchip: add overlay for the WiFi/BT module on Sige5 v1.2 Alexey Charkov
2025-06-16 21:46 ` [PATCH v2 0/4] arm64: dts: rockchip: enable further peripherals on ArmSoM Sige5 Rob Herring (Arm)
2025-06-17  6:54   ` Alexey Charkov
2025-06-19 21:17 ` Heiko Stuebner
2025-06-20  8:40   ` Alexey Charkov
2025-06-20  8:44     ` Heiko Stuebner
2025-06-20 10:10       ` Diederik de Haas [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=DARA1V0ITPV5.T24DK4TVI0W7@cknow.org \
    --to=didi.debian@cknow.org \
    --cc=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=stable@vger.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