From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>, Tao Ren <taoren@meta.com>,
rentao.bupt@gmail.com
Subject: Re: [PATCH v4 00/13] ARM: dts: aspeed: Add Meta Darwin dts
Date: Thu, 31 Jul 2025 13:02:04 +0930 [thread overview]
Message-ID: <175393272444.1011263.10036967590309258484.b4-ty@codeconstruct.com.au> (raw)
In-Reply-To: <20250728055618.61616-1-rentao.bupt@gmail.com>
On Sun, 27 Jul 2025 22:56:02 -0700, rentao.bupt@gmail.com wrote:
> From: Tao Ren <rentao.bupt@gmail.com>
>
> The patch series introduces the initial device tree for Meta/Facebook
> Darwin AST2600 BMC.
>
> Patches #1, #2 and #3 fixes the DTB warnings in wedge400/fuji dts and
> ast2600-facebook-netbmc-common.dtsi.
>
> [...]
Thanks, I've applied this to the BMC tree.
--
Andrew Jeffery <andrew@codeconstruct.com.au>
prev parent reply other threads:[~2025-07-31 3:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 5:56 rentao.bupt
2025-07-28 5:56 ` [PATCH v4 01/13] ARM: dts: aspeed: wedge400: Fix DTB warnings rentao.bupt
2025-07-28 5:56 ` [PATCH v4 02/13] ARM: dts: aspeed: fuji: " rentao.bupt
2025-07-28 5:56 ` [PATCH v4 03/13] ARM: dts: aspeed: Fix DTB warnings in ast2600-facebook-netbmc-common.dtsi rentao.bupt
2025-07-28 5:56 ` [PATCH v4 04/13] ARM: dts: aspeed: Move eMMC out of ast2600-facebook-netbmc-common.dtsi rentao.bupt
2025-07-28 5:56 ` [PATCH v4 05/13] ARM: dts: aspeed: Add facebook-bmc-flash-layout-128-data64.dtsi rentao.bupt
2025-07-28 5:56 ` [PATCH v4 06/13] dt-bindings: arm: aspeed: add Facebook Wedge400-data64 board rentao.bupt
2025-07-28 5:56 ` [PATCH v4 07/13] ARM: dts: aspeed: Add Facebook Wedge400-data64 (AST2500) BMC rentao.bupt
2025-07-28 5:56 ` [PATCH v4 08/13] ARM: dts: aspeed: wedge400: Include wedge400-data64.dts rentao.bupt
2025-07-28 5:56 ` [PATCH v4 09/13] dt-bindings: arm: aspeed: add Facebook Fuji-data64 board rentao.bupt
2025-07-30 20:55 ` Rob Herring (Arm)
2025-07-28 5:56 ` [PATCH v4 10/13] ARM: dts: aspeed: Add Facebook Fuji-data64 (AST2600) Board rentao.bupt
2025-07-28 5:56 ` [PATCH v4 11/13] ARM: dts: aspeed: facebook-fuji: Include facebook-fuji-data64.dts rentao.bupt
2025-10-14 0:20 ` Guenter Roeck
2025-10-14 1:15 ` Tao Ren
2025-10-14 3:20 ` Guenter Roeck
2025-10-14 3:44 ` Guenter Roeck
2025-10-14 4:09 ` Tao Ren
2025-10-14 4:35 ` Guenter Roeck
2025-10-14 4:45 ` Tao Ren
2025-10-14 12:08 ` Andrew Lunn
2025-10-14 14:49 ` Guenter Roeck
2025-10-14 15:11 ` Andrew Lunn
2025-10-14 16:39 ` Guenter Roeck
2025-10-14 19:14 ` Andrew Lunn
2025-10-14 22:39 ` Tao Ren
2025-10-15 0:12 ` Andrew Lunn
2025-07-28 5:56 ` [PATCH v4 12/13] dt-bindings: arm: aspeed: add Facebook Darwin board rentao.bupt
2025-07-28 5:56 ` [PATCH v4 13/13] ARM: dts: aspeed: Add Facebook Darwin (AST2600) BMC rentao.bupt
2025-07-31 3:32 ` 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=175393272444.1011263.10036967590309258484.b4-ty@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--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=rentao.bupt@gmail.com \
--cc=robh@kernel.org \
--cc=taoren@meta.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®