public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct•com.au>
To: soc <soc@lists•linux.dev>
Cc: linux-arm-kernel@lists•infradead.org, openbmc@lists•ozlabs.org,
	 linux-kernel@vger•kernel.org, Joel Stanley <joel@jms•id.au>
Subject: [GIT PULL] nuvoton: First batch of arm64 devicetree changes for v7.2
Date: Wed, 03 Jun 2026 11:25:29 +0930	[thread overview]
Message-ID: <0743460993783da99c633acbfb84bfe065cb303d.camel@codeconstruct.com.au> (raw)

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git tags/nuvoton-7.2-devicetree-0

for you to fetch changes up to eae82b6e8c2399892e145195cae9aaa0b960fdaf:

  arm64: dts: nuvoton: Add Ethernet nodes (2026-05-18 23:18:01 +0930)

----------------------------------------------------------------
nuvoton: First batch of arm64 devicetree changes for v7.2

Just the one patch adding ethernet nodes for the MA35D1 development board.

----------------------------------------------------------------
Joey Lu (1):
      arm64: dts: nuvoton: Add Ethernet nodes

 arch/arm64/boot/dts/nuvoton/ma35d1-iot-512m.dts | 25 +++++++++++++++++++++++++
 arch/arm64/boot/dts/nuvoton/ma35d1-som-256m.dts | 24 ++++++++++++++++++++++++
 arch/arm64/boot/dts/nuvoton/ma35d1.dtsi         | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 101 insertions(+)



                 reply	other threads:[~2026-06-03  1:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0743460993783da99c633acbfb84bfe065cb303d.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct$(echo .)com.au \
    --cc=joel@jms$(echo .)id.au \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=openbmc@lists$(echo .)ozlabs.org \
    --cc=soc@lists$(echo .)linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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