From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rob Herring <robh@kernel.org>
Cc: Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Tali Perry <tali.perry1@gmail.com>,
Patrick Venture <venture@google.com>,
Nancy Yuen <yuenn@google.com>,
Benjamin Fair <benjaminfair@google.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: nuvoton: Add missing "device_type" property on memory node
Date: Fri, 09 Jan 2026 11:39:50 +1030 [thread overview]
Message-ID: <d6ca5544da6f90a72dde334c4d76270fa9db9469.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAL_JsqL2ZS_D-ZUGRmJ6=dhuAAfoTUoC3CNsP4_FBat160dCVw@mail.gmail.com>
On Thu, 2026-01-08 at 08:56 -0600, Rob Herring wrote:
> On Thu, Jan 8, 2026 at 3:28 AM Andrew Jeffery
> <andrew@codeconstruct.com.au> wrote:
> >
> > On Mon, 05 Jan 2026 13:32:31 -0600, Rob Herring (Arm) wrote:
> > > "device_type" is required for memory nodes, but is missing on Nuvoton
> > > npcm845-evb.
> > >
> > >
> >
> > Thanks, I've applied this to the BMC tree.
>
> I didn't realize Nuvoton and Aspeed are 1 tree now. Should MAINTAINERS
> be updated?
Yeah, it should. I've sent this:
https://lore.kernel.org/all/20260109-npcm-arch-maintainer-v1-1-a0ec6aee22fb@codeconstruct.com.au/
Andrew
prev parent reply other threads:[~2026-01-09 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 19:32 [PATCH] arm64: dts: nuvoton: Add missing "device_type" property on memory node Rob Herring (Arm)
2026-01-08 7:09 ` Andrew Jeffery
2026-01-08 8:58 ` Andrew Jeffery
2026-01-08 15:02 ` Rob Herring
2026-01-08 9:28 ` Andrew Jeffery
2026-01-08 14:56 ` Rob Herring
2026-01-09 1:09 ` Andrew Jeffery [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=d6ca5544da6f90a72dde334c4d76270fa9db9469.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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