Devicetree
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	"J. Neuschäfer" <j.ne@posteo.net>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add missing model properties to PowerPC DTs
Date: Sat, 20 Jun 2026 03:29:24 +0530	[thread overview]
Message-ID: <178190618779.653308.915690556470586356.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260313-ppc-model-v1-0-bf19b3d1b65d@posteo.net>

On Fri, 13 Mar 2026 11:14:22 +0100, J. Neuschäfer wrote:
> 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.
> 
> 
> [...]

Applied to powerpc/next.

[1/2] powerpc: dts: mpc8315erdb: Add missing model property
      https://git.kernel.org/powerpc/c/d16cb0a9a42f7478c039ecaeba241872bc0b567a
[2/2] powerpc: dts: Add missing model properties
      https://git.kernel.org/powerpc/c/ec07a2f1d337dd5a816431724a876026296369a8

cheers

      parent reply	other threads:[~2026-06-19 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 10:14 [PATCH 0/2] Add missing model properties to PowerPC DTs J. Neuschäfer via B4 Relay
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
2026-06-19 21:59 ` Madhavan Srinivasan [this message]

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=178190618779.653308.915690556470586356.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --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=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