From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Jacky Huang <jackyhuang@nvidia.com>
Cc: joel@jms.id.au, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, ryan_chen@aspeedtech.com,
billy_tsai@aspeedtech.com, 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 v2 2/2] ARM: dts: aspeed: Add NVIDIA MGX Vera C2 BMC
Date: Mon, 16 Nov 2026 09:46:14 +1030 [thread overview]
Message-ID: <91dd4caa78cff5961b5617958f4f7985ff55724c.camel@codeconstruct.com.au> (raw)
In-Reply-To: <179455982636.2173009.10261089569510079520@nvidia.com>
On Fri, 2026-11-13 at 16:57 +0800, Jacky Huang wrote:
> Hi Andrew,
>
> Thanks for clarifying. My previous description did not explain the
> purpose of the platform. I would like to include the following
> description in the v3 commit message:
>
> NVIDIA MGX Vera C2 is a dual-socket, air-cooled 2U server reference
> platform based on NVIDIA Vera CPUs. It provides a reference design
> for partners to build and customize Vera-based servers using the
> MGX modular architecture.
>
> I will also include the following public links covering the MGX
> architecture and Vera CPU:
>
> https://www.nvidia.com/en-us/data-center/products/mgx/
> https://www.nvidia.com/en-us/data-center/vera-cpu/
>
> Hope this can help others better understand the role NVIDIA envisions
> for this platform.
Yes, thanks for the extra details.
Andrew
next prev parent reply other threads:[~2026-11-15 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 11:47 [PATCH v2 0/2] ARM: dts: aspeed: Add NVIDIA MGX Vera C2 BMC support Jacky Huang
2026-11-03 11:47 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: Add NVIDIA MGX Vera C2 BMC Jacky Huang
2026-11-03 11:47 ` [PATCH v2 2/2] ARM: dts: " Jacky Huang
2026-11-09 6:24 ` Andrew Jeffery
2026-11-11 9:32 ` Jacky Huang
2026-11-11 23:29 ` Andrew Jeffery
2026-11-13 8:57 ` Jacky Huang
2026-11-13 17:41 ` Jacky Huang
2026-11-15 23:16 ` Andrew Jeffery [this message]
2026-11-11 1:51 ` Andrew Lunn
2026-11-12 8:19 ` Jacky 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=91dd4caa78cff5961b5617958f4f7985ff55724c.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jackyhuang@nvidia.com \
--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=openbmc@lists.ozlabs.org \
--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