mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Thu, 12 Nov 2026 09:59:56 +1030	[thread overview]
Message-ID: <42bb0b817905637239c16b94a562254cd0e6a644.camel@codeconstruct.com.au> (raw)
In-Reply-To: <179438627442.2016371.12057101111349178921@nvidia.com>

On Wed, 2026-11-11 at 17:32 +0800, Jacky Huang wrote:
> Hi Andrew,
> 
> Thanks for taking the time to review this.
> 
> > Can you please expand the description of the platform? Why was it
> > designed and built? What's its purpose?
> 
> The NVIDIA MGX Vera C2 is a Vera CPU-based server platform. I will
> expand the description in v3 to clarify its purpose.

Thanks. Just to make sure we're on the same page, I feel stating that
'NVIDIA MGX Vera C2' is 'Vera-based' doesn't add any new information as
it's already in the name. Describing the purpose would give better
insight.

I'm after a helpful description in the commit message for the purpose
of summarising the content of the branch when I do a pull-request. 'Add
support for more platforms' doesn't really cut it there.

If the platform is described on the web by e.g. marketing material,
please include the link.


Andrew

  reply	other threads:[~2026-11-11 23:30 UTC|newest]

Thread overview: 7+ 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 [this message]
2026-11-11  1:51   ` Andrew Lunn

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=42bb0b817905637239c16b94a562254cd0e6a644.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
all inboxes | Powered by JetHome®