From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Kevin Tung <kevin.tung.openbmc@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Amithash Prasasd <amithash@meta.com>,
Kevin Tung <Kevin.Tung@quantatw.com>,
Ken Chen <Ken.Chen@quantatw.com>,
Leo Yang <Leo-Yang@quantatw.com>
Subject: Re: [PATCH v3 0/2] Add Meta (Facebook) Yosemite5 BMC (AST2600)
Date: Fri, 17 Oct 2025 15:37:55 +1030 [thread overview]
Message-ID: <a96786b9020ad278fbda8c2007ad1c98ca41a4a7.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251001-yv5_add_dts-v3-0-54190fbc0785@gmail.com>
On Wed, 2025-10-01 at 16:47 +0800, Kevin Tung wrote:
> Summary:
> Add device tree for the Meta (Facebook) Yosemite5 compute node,
> based on the AST2600 BMC.
>
> The Yosemite5 platform provides monitoring of voltages, power,
> temperatures, and other critical parameters across the motherboard,
> CXL board, E1.S expansion board, and NIC components. The BMC also
> logs relevant events and performs appropriate system actions in
> response to abnormal conditions.
>
> Signed-off-by: Kevin Tung <kevin.tung.openbmc@gmail.com>
Thanks, I've applied this to the BMC tree.
Andrew
prev parent reply other threads:[~2025-10-17 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 8:47 [PATCH v3 0/2] Add Meta (Facebook) Yosemite5 BMC (AST2600) Kevin Tung
2025-10-01 8:47 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: add Meta Yosemite5 board Kevin Tung
2025-10-01 18:33 ` Conor Dooley
2025-10-02 4:23 ` Kevin Tung
2025-10-02 18:35 ` Conor Dooley
2025-10-03 1:31 ` Kevin Tung
2025-10-01 8:47 ` [PATCH v3 2/2] ARM: dts: aspeed: yosemite5: Add Meta Yosemite5 BMC Kevin Tung
2025-10-17 5:07 ` Andrew Jeffery [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=a96786b9020ad278fbda8c2007ad1c98ca41a4a7.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Ken.Chen@quantatw.com \
--cc=Kevin.Tung@quantatw.com \
--cc=Leo-Yang@quantatw.com \
--cc=amithash@meta.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=joel@jms.id.au \
--cc=kevin.tung.openbmc@gmail.com \
--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=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).