From: Tan Siewert <tan.siewert@9elements.com>
To: Prasanth <prasanth.padarthi10@gmail.com>
Cc: joel@jms.id.au, andrew@codeconstruct.com.au, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
ryan_chen@aspeedtech.com, billy_tsai@aspeedtech.com,
andrew@lunn.ch, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC support
Date: Tue, 22 Sep 2026 15:27:53 +0200 [thread overview]
Message-ID: <968796d6-811d-434a-a230-f05da451252c@9elements.com> (raw)
In-Reply-To: <CAMFFDGjJcmpaQYHe=F+jpstbdk9-uXPKkBxLkJqAJRiyyTkBvg@mail.gmail.com>
On 9/22/26 3:26 PM, Prasanth wrote:
> Hi Tan,
>
> Thank you for catching these issues.
>
> You're correct about the defconfig. I used `aspeed_g5_defconfig` for
> the DTB build and incorrectly reported it as validation for the
> AST2600. I'll rebuild using the appropriate AST2600 configuration and
> correct the statement in the next revision.
>
> I'll also carry forward Andrew's Reviewed-by trailer for the unchanged
> MAC0 and MDIO nodes, preserving the scope of his review.
Andrew has already resent the trailer, so no need to send another
revision for that.
Tan
prev parent reply other threads:[~2026-09-22 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 12:34 Prasanth Kumar Padarthi
2026-09-22 12:34 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: Add ASRock Rack B650D4U Prasanth Kumar Padarthi
2026-09-22 12:35 ` [PATCH v7 2/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC Prasanth Kumar Padarthi
2026-09-22 12:50 ` Andrew Lunn
2026-09-22 13:28 ` Tan Siewert
2026-09-22 16:03 ` Prasanth
2026-09-22 13:21 ` [PATCH v7 0/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC support Tan Siewert
2026-09-22 13:26 ` Prasanth
2026-09-22 13:27 ` Tan Siewert [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=968796d6-811d-434a-a230-f05da451252c@9elements.com \
--to=tan.siewert@9elements.com \
--cc=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=billy_tsai@aspeedtech.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=prasanth.padarthi10@gmail.com \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.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
all inboxes | Powered by JetHome®