linux-kernel - Re: [PATCH 0/9] arm64: introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <09b1318e-21dc-4354-8733-866b70696295@app.fastmail.com>
Date: Thu, 25 Sep 2025 09:06:54 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "yangzh0906@...ndersoft.com" <yangzh0906@...ndersoft.com>,
 "Rob Herring" <robh@...nel.org>, "Krzysztof Kozlowski" <krzk+dt@...nel.org>,
 "Conor Dooley" <conor+dt@...nel.org>, "gordon.ge" <gordon.ge@....ai>,
 bst-upstream <bst-upstream@...ai.top>,
 "Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>,
 "Ulf Hansson" <ulf.hansson@...aro.org>,
 "Adrian Hunter" <adrian.hunter@...el.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org,
 "linux-mmc @ vger . kernel . org" <linux-mmc@...r.kernel.org>,
 soc@...ts.linux.dev, "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH 0/9] arm64: introduce Black Sesame Technologies C1200 SoC and
 CDCU1.0 board

On Tue, Sep 23, 2025, at 08:10, Albert Yang wrote:
> This patch series introduces comprehensive support for Black Sesame 
> Technologies
> (BST) C1200 SoC and CDCU1.0 ADAS 4C2G board. BST is a leading 
> automotive-grade
> computing SoC provider focusing on intelligent driving, computer 
> vision, and AI
> capabilities for ADAS and autonomous driving applications. You can find 
> more information
> about the SoC and related boards at: https://bst.ai

Hi Albert,

I see you submitted the series to soc@...ts.linux.dev, which would
normally indicate that it has been fully reviewed and is ready
to be merged.

I'd be happy to merge the actual SoC portions in arch/arm64 as they
do seem to be ready, and for a new SoC support I sometimes merge
in required driver changes with a subsystem (uart, irqchip, clk, ...)
maintainer's Ack as well. However the MMC driver portions in patches
4-6 don't really fall into that category, as there has not been
any Ack for this version yet, and MMC is not one of the subsystems
we normally make this exception for.

Given the current timing, I would suggest that you respin the
series for 6.19 once 6.18-rc1 is out and leave out those three
patches in the submission to soc@...ts.linux.dev.

If the MMC driver gets merged for 6.19, it's ok to keep the
sdhci device nodes in the dtsi file here, but to make things
easier, you can also leave out those nodes in the initial
submission and send this as a follow-up patch to
soc@...ts.linux.dev once the driver is actually merged.

     Arnd