From: Andrew Lunn <andrew@lunn.ch>
To: Willie Thai <wthai@nvidia.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au, kees@kernel.org,
tony.luck@intel.com, gpiccoli@igalia.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, openbmc@lists.ozlabs.org,
leohu@nvidia.com, tingkaic@nvidia.com, dkodihalli@nvidia.com,
Mars Yang <maryang@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH v3 1/2] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC
Date: Thu, 20 Mar 2025 17:54:59 +0100 [thread overview]
Message-ID: <fbf6a89b-80c4-47f3-9dad-2725c040e041@lunn.ch> (raw)
In-Reply-To: <20250320164633.101331-2-wthai@nvidia.com>
> - Skip mac setting and wait till the delay issue in phy-mode fix from Aspeed SOC vendor side [Andrew]
For this part only:
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-03-20 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 16:46 [PATCH v3 0/2] " Willie Thai
2025-03-20 16:46 ` [PATCH v3 1/2] ARM: dts: aspeed: " Willie Thai
2025-03-20 16:54 ` Andrew Lunn [this message]
2025-03-21 7:44 ` Krzysztof Kozlowski
2025-03-20 16:46 ` [PATCH v3 2/2] dt-bindings: arm: aspeed: add " Willie Thai
2025-03-21 1:06 ` Andrew Jeffery
2025-03-21 5:27 ` Willie Thai
2025-03-21 9:40 ` Krzysztof Kozlowski
2025-03-20 18:26 ` [PATCH v3 0/2] Add device tree for " Rob Herring (Arm)
2025-03-21 1:06 ` Andrew Jeffery
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=fbf6a89b-80c4-47f3-9dad-2725c040e041@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=gpiccoli@igalia.com \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maryang@nvidia.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh@kernel.org \
--cc=tingkaic@nvidia.com \
--cc=tony.luck@intel.com \
--cc=wthai@nvidia.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®