From: Kanak Shilledar <Kanak.Shilledar@axis.com>
To: "alex@ghiti.fr" <alex@ghiti.fr>,
"guoren@kernel.org" <guoren@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"pjw@kernel.org" <pjw@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"fustini@kernel.org" <fustini@kernel.org>,
"wefu@redhat.com" <wefu@redhat.com>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] riscv: dts: thead: Cleanup with dt-check-style
Date: Mon, 26 Oct 2026 13:02:22 +0000 [thread overview]
Message-ID: <55208f641473e0714e4509fd5d071343b3a0de98.camel@axis.com> (raw)
In-Reply-To: <20261002-fix-dts-th1520-v1-0-9a8810091d47@axis.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Fri, 2026-10-02 at 15:43 +0200, Kanak Shilledar wrote:
> Fix almost all warnings thrown by dt-check-style after krzk's updates
> to the tool [1] when run under the strict mode. There are still a few
> warnings remaining which are documented in the relevant commit
> message.
> By doing this the files become easier to read and maintain.
>
> After this patch series only the following warnings are thrown:
>
> arch/riscv/boot/dts/thead/th1520.dtsi:221: [child-name-
> order] child node 'oscillator' out of name order
> arch/riscv/boot/dts/thead/th1520.dtsi:227: [child-name-
> order] child node '32k-oscillator' out of name order
> arch/riscv/boot/dts/thead/th1520.dtsi:248: [property-name]
> property name "snps,wr_osr_lmt" is using discouraged style
> arch/riscv/boot/dts/thead/th1520.dtsi:249: [property-name]
> property name "snps,rd_osr_lmt" is using discouraged style
> arch/riscv/boot/dts/thead/th1520.dtsi:253: [child-name-
> order] child node 'aon' out of name order
>
> These are left for future work as they create a very large diff.
>
> [1]
> https://github.com/krzk/linux/tree/b4/dts-style-checker-blank-lines
>
> Signed-off-by: Kanak Shilledar <kanak.shilledar@axis.com>
> ---
Friendly ping :)
Best Regards,
Kanak Shilledar
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-26 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 13:43 Kanak Shilledar
2026-10-02 13:43 ` [PATCH 1/4] riscv: dts: thead: beaglev-ahead: " Kanak Shilledar
2026-10-02 13:43 ` [PATCH 2/4] riscv: dts: thead: th1520: " Kanak Shilledar
2026-10-02 13:43 ` [PATCH 3/4] riscv: dts: th1520-lichee-module-4a: " Kanak Shilledar
2026-10-02 13:43 ` [PATCH 4/4] riscv: dts: thead: th1520-lichee-pi-4a: " Kanak Shilledar
2026-10-26 13:02 ` Kanak Shilledar [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=55208f641473e0714e4509fd5d071343b3a0de98.camel@axis.com \
--to=kanak.shilledar@axis.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=guoren@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=wefu@redhat.com \
/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®