mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacky Huang <jackyhuang@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: Jacky Huang <jackyhuang@nvidia.com>,
	<andrew@codeconstruct.com.au>, <joel@jms.id.au>,
	<krzysztof.kozlowski@oss.qualcomm.com>, <conor+dt@kernel.org>,
	<andrew@lunn.ch>, <devicetree@vger.kernel.org>,
	<linux-aspeed@lists.ozlabs.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v4 2/2] ARM: dts: aspeed: Add NVIDIA VR-NVL BMC
Date: Fri, 16 Oct 2026 14:49:53 +0900	[thread overview]
Message-ID: <20261016055117.59404-1-jackyhuang@nvidia.com> (raw)
In-Reply-To: <CAL_JsqKx4OEM-asdvs1wUiP3FFObzJHZtNTtqiwtcRhJ5CPRyQ@mail.gmail.com>

Hi Rob,

> A board level component shouldn't be in the SoC .dtsi file.

I submitted a separate cleanup series to address this. The series
updates the AST2600 board files and vendor common DTSI files to
declare the flash devices they use, then removes the shared flash
nodes from aspeed-g6.dtsi:

https://lore.kernel.org/all/20260813102233.3088939-1-jackyhuang@nvidia.com/

I plan to base v5 of the VR-NVL DTS series on this cleanup.

Thanks,
Jacky

      parent reply	other threads:[~2026-10-16  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  8:55 [PATCH v4 0/2] Add device tree for " Jacky Huang
2026-07-28  8:55 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: Add " Jacky Huang
2026-07-28  8:55 ` [PATCH v4 2/2] ARM: dts: " Jacky Huang
2026-07-28 14:39   ` Rob Herring
2026-07-29  6:06     ` Jacky Huang
2026-07-29  6:16       ` Krzysztof Kozlowski
2026-07-29  8:40         ` Jacky Huang
2026-07-29 13:17       ` Rob Herring
2026-07-30 10:24         ` Jacky Huang
2026-10-16  5:49         ` Jacky Huang [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=20261016055117.59404-1-jackyhuang@nvidia.com \
    --to=jackyhuang@nvidia.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --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
all inboxes | Powered by JetHome®