From: "Rob Herring (Arm)" <robh@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>
Cc: linux-arm-kernel@lists.infradead.org,
Eddie James <eajames@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Lee Jones <lee@kernel.org>,
devicetree@vger.kernel.org, Joel Stanley <joel@jms.id.au>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-aspeed@lists.ozlabs.org,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2 2/4] dt-bindings: mfd: aspeed: Add AST2700 SCU compatibles
Date: Mon, 1 Sep 2025 15:28:53 -0500 [thread overview]
Message-ID: <175675853255.286945.13351927869745277477.robh@kernel.org> (raw)
In-Reply-To: <20250831021438.976893-3-ryan_chen@aspeedtech.com>
On Sun, 31 Aug 2025 10:14:36 +0800, Ryan Chen wrote:
> Add SCU interrupt controller compatible strings for the AST2700 SoC:
> scu-ic0 to 3. This extends the MFD binding to support AST2700-based
> platforms.
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-01 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 2:14 [PATCH v2 0/4] irqchip: Add support for Aspeed AST2700 SCU interrupt controller Ryan Chen
2025-08-31 2:14 ` [PATCH v2 1/4] irqchip/aspeed-scu-ic: Refactor driver to support variant-based initialization Ryan Chen
2025-09-02 12:56 ` Thomas Gleixner
2025-09-03 10:03 ` Ryan Chen
2025-08-31 2:14 ` [PATCH v2 2/4] dt-bindings: mfd: aspeed: Add AST2700 SCU compatibles Ryan Chen
2025-09-01 20:28 ` Rob Herring (Arm) [this message]
2025-08-31 2:14 ` [PATCH v2 3/4] dt-bindings: interrupt-controller: aspeed: Add AST2700 SCU IC compatibles Ryan Chen
2025-09-01 20:29 ` Rob Herring (Arm)
2025-08-31 2:14 ` [PATCH v2 4/4] irqchip/aspeed-scu-ic: Add support AST2700 SCU interrupt controllers Ryan Chen
2025-09-02 13:07 ` Thomas Gleixner
2025-09-05 5:55 ` Ryan Chen
2025-09-05 7:47 ` Thomas Gleixner
2025-09-05 8:57 ` Ryan Chen
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=175675853255.286945.13351927869745277477.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tglx@linutronix.de \
/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