From: Cosmo Chou <chou.cosmo@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
cosmo.chou@quantatw.com, Cosmo Chou <chou.cosmo@gmail.com>
Subject: [PATCH v2 0/5] ARM: dts: aspeed: bletchley: Fix dt-schema warnings
Date: Wed, 17 Dec 2025 10:39:33 +0800 [thread overview]
Message-ID: <20251217023938.445721-1-chou.cosmo@gmail.com> (raw)
This series fixes dt-schema validation warnings by using generic node
names, correcting GPIO property suffixes, and removing unsupported
properties. No functional changes.
Changes in v2:
- Split single patch into 5 separate patches by change type
Cosmo Chou (5):
ARM: dts: aspeed: bletchley: Use generic node names
ARM: dts: aspeed: bletchley: Fix SPI GPIO property names
ARM: dts: aspeed: bletchley: Remove unused pca9539 properties
ARM: dts: aspeed: bletchley: Remove unused i2c13 property
ARM: dts: aspeed: bletchley: Fix ADC vref property names
.../aspeed/aspeed-bmc-facebook-bletchley.dts | 100 ++++++++++--------
1 file changed, 54 insertions(+), 46 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-17 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 2:39 Cosmo Chou [this message]
2025-12-17 2:39 ` [PATCH v2 1/5] ARM: dts: aspeed: bletchley: Use generic node names Cosmo Chou
2025-12-17 2:39 ` [PATCH v2 2/5] ARM: dts: aspeed: bletchley: Fix SPI GPIO property names Cosmo Chou
2025-12-17 2:39 ` [PATCH v2 3/5] ARM: dts: aspeed: bletchley: Remove unused pca9539 properties Cosmo Chou
2025-12-17 2:39 ` [PATCH v2 4/5] ARM: dts: aspeed: bletchley: Remove unused i2c13 property Cosmo Chou
2025-12-17 2:39 ` [PATCH v2 5/5] ARM: dts: aspeed: bletchley: Fix ADC vref property names Cosmo Chou
2025-12-17 8:31 ` [PATCH v2 0/5] ARM: dts: aspeed: bletchley: Fix dt-schema warnings Andrew Jeffery
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=20251217023938.445721-1-chou.cosmo@gmail.com \
--to=chou.cosmo@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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