From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Ryan Chen" <ryan_chen@aspeedtech.com>,
"Arnd Bergmann" <arnd@arndb.de>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@oss.qualcomm.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Nishanth Menon" <nm@ti.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Taniya Das" <quic_tdas@quicinc.com>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Eric Biggers" <ebiggers@google.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"soc@lists.linux.dev" <soc@lists.linux.dev>,
"Mo Elbadry" <elbadrym@google.com>,
"Rom Lemarchand" <romlem@google.com>,
"William Kennington" <wak@google.com>,
"Yuxiao Zhang" <yuxiaozhang@google.com>,
"wthai@nvidia.com" <wthai@nvidia.com>,
"leohu@nvidia.com" <leohu@nvidia.com>,
"dkodihalli@nvidia.com" <dkodihalli@nvidia.com>,
"spuranik@nvidia.com" <spuranik@nvidia.com>
Subject: Re: [PATCH v5 0/5] Introduce ASPEED AST2700 BMC SoC
Date: Mon, 20 Oct 2025 08:40:23 +0200 [thread overview]
Message-ID: <2eb2d833-03e0-4570-8979-3a28d708b21f@kernel.org> (raw)
In-Reply-To: <OS8PR06MB7541AEC5560E3445C33009BEF21FA@OS8PR06MB7541.apcprd06.prod.outlook.com>
On 25/09/2025 10:00, Ryan Chen wrote:
>> Subject: Re: [PATCH v5 0/5] Introduce ASPEED AST2700 BMC SoC
>>
>> On Mon, Sep 1, 2025, at 05:13, Ryan Chen wrote:
>>> This introduces initial support for the Aspeed AST2700 SoC and the
>>> AST2700 Evaluation Board (EVB) to the Linux kernel. The AST27XX is the
>>> 8th generation Baseboard Management Controller (BMC) SoC from Aspeed,
>>> featuring improved performance, enhanced security, and expanded I/O
>>> capabilities compared to previous generations.
>>>
>>> AST27XX SOC Family
>>> - https://www.aspeedtech.com/server_ast2700/
>>> - https://www.aspeedtech.com/server_ast2720/
>>> - https://www.aspeedtech.com/server_ast2750/
>>
>> Hi Ryan,
>>
>> Thanks for you submission earlier. I see that you had sent the series to several
>> lists including soc@lists.linux.dev, which is what I use to keep track of patches
>> that have been successfully reviewed and that are ready to be merged through
>> the soc tree.
>>
>> Unless you have been told to send it here by Joel and Andrew, I assume that
>> they will pick up the series through the "bmc"
>> tree once they are happy with it like they do with the 32-bit Aspeed SoC
>> (ast24xx/25xx/26xx) patches, and I have dropped the series from
>> https://patchwork.kernel.org/project/linux-soc
>> now.
>>
>> For future submission, please send the patches only "to"
>> them, with the other people in the "cc" field to avoid this confusion, and leave
>> out the "soc@lists.linux.dev"
>> recipient. You can add me as arnd@arndb.de to the Cc list for reviews though.
>>
>> Please also add a patch that changes the MAINTAINERS entry to reflect the
>> added arch/arm64 contents.
>>
>> Arnd
>
> Hello Arnd,
> Thanks your notify. I will remove soc@lists.linux.dev, in next patch.
No, this patchset still has known (reported) warnings/bugs, which need
to be addressed here before merging it.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-20 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 3:13 [PATCH v5 0/5] Introduce ASPEED AST2700 BMC SoC Ryan Chen
2025-09-01 3:13 ` [PATCH v5 1/5] dt-bindings: arm: aspeed: Add AST2700 board compatible Ryan Chen
2025-09-01 3:13 ` [PATCH v5 2/5] arm64: Kconfig: Add Aspeed SoC family (ast27XX) Kconfig support Ryan Chen
2025-09-01 3:13 ` [PATCH v5 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device tree Ryan Chen
2025-09-01 3:13 ` [PATCH v5 4/5] arm64: dts: aspeed: Add AST2700 Evaluation Board Ryan Chen
2025-09-01 5:52 ` Krzysztof Kozlowski
2025-09-02 0:10 ` Ryan Chen
2025-09-01 3:13 ` [PATCH v5 5/5] arm64: configs: Update defconfig for AST2700 platform support Ryan Chen
2025-09-01 5:26 ` Krzysztof Kozlowski
2025-09-02 13:18 ` [PATCH v5 0/5] Introduce ASPEED AST2700 BMC SoC Rob Herring (Arm)
2025-09-25 7:50 ` Arnd Bergmann
2025-09-25 8:00 ` Ryan Chen
2025-10-20 6:40 ` Krzysztof Kozlowski [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=2eb2d833-03e0-4570-8979-3a28d708b21f@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=ebiggers@google.com \
--cc=elbadrym@google.com \
--cc=geert@linux-m68k.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=romlem@google.com \
--cc=ryan_chen@aspeedtech.com \
--cc=soc@lists.linux.dev \
--cc=spuranik@nvidia.com \
--cc=wak@google.com \
--cc=will@kernel.org \
--cc=wthai@nvidia.com \
--cc=yuxiaozhang@google.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).