From: "J. Neuschäfer via B4 Relay" <devnull+j.ne.posteo.net@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, "J. Neuschäfer" <j.ne@posteo.net>
Subject: [PATCH 0/2] Add missing model properties to PowerPC DTs
Date: Fri, 13 Mar 2026 11:14:22 +0100 [thread overview]
Message-ID: <20260313-ppc-model-v1-0-bf19b3d1b65d@posteo.net> (raw)
The devicetree spec requires a /model property, but many of the powerpc
devicetrees don't have one. This series is an attempt to fix it.
One practical advantage is that scripts/make_fit.py will no longer throw
an error when invoked with the powerpc DTs.
Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
---
J. Neuschäfer (2):
powerpc: dts: mpc8315erdb: Add missing model property
powerpc: dts: Add missing model properties
arch/powerpc/boot/dts/mpc8308_p1m.dts | 1 +
arch/powerpc/boot/dts/mpc8308rdb.dts | 1 +
arch/powerpc/boot/dts/mpc8315erdb.dts | 1 +
arch/powerpc/boot/dts/mpc836x_rdk.dts | 1 +
arch/powerpc/boot/dts/mpc8377_rdb.dts | 1 +
arch/powerpc/boot/dts/mpc8377_wlan.dts | 1 +
arch/powerpc/boot/dts/mpc8378_rdb.dts | 1 +
arch/powerpc/boot/dts/mpc8379_rdb.dts | 1 +
8 files changed, 8 insertions(+)
---
base-commit: c9849854bc5ce9afca21f97bb17b7ff763fdf159
change-id: 20260103-ppc-model-7505378b9893
Best regards,
--
J. Neuschäfer <j.ne@posteo.net>
next reply other threads:[~2026-03-13 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 10:14 J. Neuschäfer via B4 Relay [this message]
2026-03-13 10:14 ` [PATCH 1/2] powerpc: dts: mpc8315erdb: Add missing model property J. Neuschäfer via B4 Relay
2026-03-13 10:14 ` [PATCH 2/2] powerpc: dts: Add missing model properties J. Neuschäfer via B4 Relay
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=20260313-ppc-model-v1-0-bf19b3d1b65d@posteo.net \
--to=devnull+j.ne.posteo.net@kernel.org \
--cc=chleroy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.ne@posteo.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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