From: sjg168@gmail.com
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Peter Shen <sjg168@gmail.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
peter.shen@amd.com
Subject: [PATCH v4 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC
Date: Fri, 7 Nov 2025 16:12:10 +0800 [thread overview]
Message-ID: <20251107-anacapa-v4-0-peter-shen-amd@sjg168> (raw)
In-Reply-To: <20251104-mellow-denim-dogfish-4affdb@kuoka>
From: Peter Shen <sjg168@gmail.com>
This patch series adds the device tree binding and the initial device tree
source file for the Facebook Anacapa BMC, which utilizes the Aspeed AST2600
SoC.
The patches configure the necessary platform peripherals and aliases for
OpenBMC usage.
---
Changes in v4:
- Addressed the fatal 'Broken DCO/email chain' issue reported by the maintainer. The Author and Signed-off-by fields in all commits are now unified to match the sender's email address (sjg168@gmail.com).
- Addressed all remaining checkpatch.pl warnings reported against v3:
- Fixed all block comment style warnings (converting to proper multi-line C-style format) and line length issues in gpio-line-names.
- Removed the un-documented "amd,helios_cpld" compatible string to eliminate the highest priority DT binding warning.
- Removed unused and commented-out device tree nodes (eeprom@53).
next prev parent reply other threads:[~2025-11-07 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:33 [PATCH v3 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC Peter Shen
2025-11-03 9:33 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: Add compatible " Peter Shen
2025-11-04 8:22 ` Krzysztof Kozlowski
2025-11-07 8:12 ` sjg168 [this message]
2025-11-07 8:22 ` [PATCH v5 0/2] ARM: dts: aspeed: Add Device Tree " Peter Shen
2025-11-07 8:38 ` Krzysztof Kozlowski
2025-11-03 9:33 ` [PATCH v3 2/2] " Peter Shen
2025-11-04 8:23 ` Krzysztof Kozlowski
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=20251107-anacapa-v4-0-peter-shen-amd@sjg168 \
--to=sjg168@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.shen@amd.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