From: Jason Hsu <jasonhell19@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au, patrick@stwcx.xyz,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: yang.chen@quantatw.com, jerry.lin@quantatw.com,
Jason Hsu <jasonhell19@gmail.com>
Subject: [PATCH v7 1/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC
Date: Fri, 6 Jun 2025 10:52:50 +0800 [thread overview]
Message-ID: <20250606025251.887953-2-jasonhell19@gmail.com> (raw)
In-Reply-To: <20250606025251.887953-1-jasonhell19@gmail.com>
Add Linux device tree related to Meta(Facebook) Ventura specific
devices connected to BMC(AST2600) SoC.Add subject prefix for the patch.
Signed-off-by: Jason Hsu <jasonhell19@gmail.com>
---
Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
index 01333ac111fb..a86b411df9a5 100644
--- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
@@ -87,6 +87,7 @@ properties:
- facebook,greatlakes-bmc
- facebook,harma-bmc
- facebook,minerva-cmc
+ - facebook,ventura-rmc
- facebook,yosemite4-bmc
- ibm,blueridge-bmc
- ibm,everest-bmc
--
2.34.1
next prev parent reply other threads:[~2025-06-06 3:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 2:52 [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason Hsu
2025-06-06 2:52 ` Jason Hsu [this message]
2025-06-06 6:50 ` [PATCH v7 1/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC Krzysztof Kozlowski
2025-06-06 2:52 ` [PATCH v7 2/2] dt-bindings: arm: aspeed: add Meta Ventura board Jason Hsu
2025-06-06 6:52 ` Krzysztof Kozlowski
2025-06-11 12:16 ` 徐傑生
2025-06-06 13:14 ` [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Rob Herring (Arm)
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=20250606025251.887953-2-jasonhell19@gmail.com \
--to=jasonhell19@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerry.lin@quantatw.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=patrick@stwcx.xyz \
--cc=robh@kernel.org \
--cc=yang.chen@quantatw.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;
as well as URLs for NNTP newsgroup(s).