From: FUKAUMI Naoki <naoki@radxa.com>
To: heiko@sntech.de
Cc: robh@kernel.org, conor+dt@kernel.org, inindev@gmail.com,
devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
linux-rockchip@lists.infradead.org, alchark@gmail.com,
FUKAUMI Naoki <naoki@radxa.com>,
krzk+dt@kernel.org, dsimic@manjaro.org
Subject: [PATCH v2 0/4] arm64: dts: rockchip: cosmetic changes for Radxa ROCK 5B
Date: Mon, 2 Dec 2024 02:32:23 +0000 [thread overview]
Message-ID: <20241202023227.2671-1-naoki@radxa.com> (raw)
this patch series sort nodes and properties, remove redundant
properties, and minor cosmetic changes.
no functional change is intended.
this patch series depend on following patch series:
"arm64: dts: rockchip: sync dts with schematic for Radxa ROCK 5B"
https://patchwork.kernel.org/project/linux-rockchip/cover/20241130004057.7432-1-naoki@radxa.com/
FUKAUMI Naoki (4):
arm64: dts: rockchip: sort nodes in .dts for Radxa ROCK 5B
arm64: dts: rockchip: sort nodes in root node for Radxa ROCK 5B
arm64: dts: rockchip: sort properties in .dts for Radxa ROCK 5B
arm64: dts: rockchip: cosmetic changes for Radxa ROCK 5B
.../boot/dts/rockchip/rk3588-rock-5b.dts | 184 ++++++++----------
1 file changed, 86 insertions(+), 98 deletions(-)
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2024-12-02 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 2:32 FUKAUMI Naoki [this message]
2024-12-02 2:32 ` [PATCH v2 1/4] arm64: dts: rockchip: sort nodes in .dts for Radxa ROCK 5B FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 2/4] arm64: dts: rockchip: sort nodes in root node " FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 3/4] arm64: dts: rockchip: sort properties in .dts " FUKAUMI Naoki
2024-12-02 2:32 ` [PATCH v2 4/4] arm64: dts: rockchip: cosmetic changes " FUKAUMI Naoki
2024-12-02 3:06 ` [PATCH v2 0/4] " Dragan Simic
2024-12-02 3:58 ` FUKAUMI Naoki
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=20241202023227.2671-1-naoki@radxa.com \
--to=naoki@radxa.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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