public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Colin Huang <u8813345@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	colin.huang2@amd.com
Subject: Re: [PATCH 2/3] ARM: dts: aspeed: anacapa: add EVT1 devicetree and point wrapper to it
Date: Wed, 8 Apr 2026 11:00:35 +0200	[thread overview]
Message-ID: <dfe798b5-6db9-4b8a-8246-ff607f5241cc@kernel.org> (raw)
In-Reply-To: <CAPBH0A-ER9-_KpknyOKTmS2sBk-xv0c016y9WsLOvZ8CjSiwCw@mail.gmail.com>

On 08/04/2026 10:52, Colin Huang wrote:
> Hi Krzysztof,
>    Thanks for reply.

Do not top post.

>    Could you let me know  what kind test I need to run?
>    Following is what I do before send.
>    * I build this dts with linux 6.6.x

v6.6? That's like 2.5 years ago.

No, you must work on recent kernel.

>    * run "b4 prep --check"

Google - how to validate DTS in Linux kernel

Best regards,
Krzysztof


  reply	other threads:[~2026-04-08  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 13:54 [PATCH 0/3] ARM: dts: aspeed: anacapa: restructure devicetree for development-phase Colin Huang
2026-04-07 13:54 ` [PATCH 1/3] dt-bindings: arm: aspeed: add Anacapa EVT1 EVT2 board Colin Huang
2026-04-07 13:54 ` [PATCH 2/3] ARM: dts: aspeed: anacapa: add EVT1 devicetree and point wrapper to it Colin Huang
2026-04-08  7:52   ` Krzysztof Kozlowski
2026-04-08  8:52     ` Colin Huang
2026-04-08  9:00       ` Krzysztof Kozlowski [this message]
2026-04-07 13:54 ` [PATCH 3/3] ARM: dts: aspeed: anacapa: add EVT2 devicetree and update wrapper Colin Huang

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=dfe798b5-6db9-4b8a-8246-ff607f5241cc@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=colin.huang2@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=u8813345@gmail.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