From: Michal Simek <michal.simek@amd.com>
To: kylebonnici <kylebonnici@proton.me>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
Peter Korsgaard <peter@korsgaard.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kyle Bonnici <kylebonnici@hotmail.com>
Subject: Re: [PATCH] Coding Style: Format arch/arm/boot/dts/xilinx
Date: Wed, 7 Jan 2026 08:49:21 +0100 [thread overview]
Message-ID: <f514d490-75d8-408e-99ba-ee44916395fc@amd.com> (raw)
In-Reply-To: <zUWWtNtMhwr9_g1C6mdaGPvyls1-H_tCHfdMuWC35MYUzv88iiaEzS9RTUiucp4QU_RhvuTGiNcl_GV684b6h4-DmdnKPeCLGKB1RHEG6G8=@proton.me>
Hi,
On 1/6/26 21:28, kylebonnici wrote:
> Hi,
>
first of all please don't do top posting.
> Thanks for the feedback.
>
> with regard to subject I am not sure in what subsystem file formatting would go (especially if we run it on even more files and more systems are modified) Your guidance would be appreciated.
arm: xilinx:
or for 64 bit version
arm64: xilinx:
>
> With regard to improving the line wrapping, can you share some examples so that I can start looking on improving this?
run it over zynqmp.dtsi file
And focus on pcie node
@@ -958,8 +979,10 @@ pcie: pcie@fd0e0000 {
<0x0 0xfd480000 0x0 0x1000>,
<0x80 0x00000000 0x0 0x10000000>;
reg-names = "breg", "pcireg", "cfg";
- ranges = <0x02000000 0x00000000 0xe0000000 0x00000000
0xe0000000 0x00000000 0x10000000>,/* non-prefetchable memory */
- <0x43000000 0x00000006 0x00000000 0x00000006
0x00000000 0x00000002 0x00000000>;/* prefetchable memory */
+ ranges = <0x02000000 0x00000000 0xe0000000 0x00000000
0xe0000000 0x00000000
+ 0x10000000>,/* non-prefetchable memory */
+ <0x43000000 0x00000006 0x00000000 0x00000006
0x00000000 0x00000002
+ 0x00000000>;/* prefetchable memory */
bus-range = <0x00 0xff>;
1. sometimes commens are using space,tab or nothing. Same style would be useful.
2. last cell on next line looks weird to me. I think you can decode
address-cells/size-cells for ranges and do indentation base on it.
>
> To run on more files I will wait for feedback from Rob, Krzysztof and Conor.
yep.
Thanks,
Michal
next prev parent reply other threads:[~2026-01-07 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:51 kylebonnici
2026-01-06 11:54 ` Michal Simek
2026-01-06 20:28 ` kylebonnici
2026-01-07 7:49 ` Michal Simek [this message]
2026-01-07 17:21 ` kylebonnici
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=f514d490-75d8-408e-99ba-ee44916395fc@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kylebonnici@hotmail.com \
--cc=kylebonnici@proton.me \
--cc=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
--cc=robh@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®