From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: soc <soc@lists.linux.dev>
Cc: linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Joel Stanley <joel@jms.id.au>
Subject: [GIT PULL] aspeed: First batch of ARM devicetree changes for 7.3
Date: Tue, 04 Aug 2026 15:06:05 +0930 [thread overview]
Message-ID: <a0dbb1b1642b5d30f01adb5f48c51e426414dc90.camel@codeconstruct.com.au> (raw)
Hello SoC maintainers,
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git aspeed-arm-7.3-devicetree-0
for you to fetch changes up to 749c34389679f8d56cb200a69b62f9a64670034f:
ARM: dts: aspeed: Correct indentation (2026-07-23 00:52:02 +0930)
----------------------------------------------------------------
aspeed: First batch of ARM devicetree changes for 7.3
No significant changes this time around. Instead, several cleanups
for Meta's San Miguel platform, along with some changes enabling
dt-check-style.
----------------------------------------------------------------
Krzysztof Kozlowski (1):
ARM: dts: aspeed: Correct indentation
Mike Hsieh (1):
ARM: dts: aspeed: sanmiguel: fix PDB HSC shunt resistor
Potin Lai (2):
ARM: dts: aspeed: sanmiguel: Fix FIO IOEXP interrupt pin
ARM: dts: aspeed: sanmiguel: Fix PWRGD_RMC_N active-low hog configuration
.../dts/aspeed/aspeed-bmc-facebook-sanmiguel.dts | 14 +-
.../aspeed/aspeed-bmc-inventec-transformers.dts | 432 ++++++++++-----------
arch/arm/boot/dts/aspeed/aspeed-bmc-opp-vesnin.dts | 2 +-
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 2 +-
4 files changed, 225 insertions(+), 225 deletions(-)
next reply other threads:[~2026-08-04 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 5:36 Andrew Jeffery [this message]
2026-08-08 20:20 ` [GIT PULL] aspeed: First batch of ARM devicetree changes for 7.3 patchwork-bot+linux-soc
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=a0dbb1b1642b5d30f01adb5f48c51e426414dc90.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.