[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <141c7d39-9f0e-4c1c-86c5-149328ab979a@app.fastmail.com>
Date: Fri, 15 Nov 2024 16:09:30 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Niko Pasaloukos" <nikolaos.pasaloukos@...ize.com>,
"Rob Herring" <robh@...nel.org>, "Krzysztof Kozlowski" <krzk+dt@...nel.org>,
"Conor Dooley" <conor+dt@...nel.org>,
"James Cowgill" <james.cowgill@...ize.com>,
"Matt Redfearn" <matthew.redfearn@...ize.com>,
"Neil Jones" <neil.jones@...ize.com>,
"Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>,
"Olof Johansson" <olof@...om.net>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"soc@...ts.linux.dev" <soc@...ts.linux.dev>
Subject: Re: [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC
On Fri, Nov 15, 2024, at 15:58, Niko Pasaloukos wrote:
> Blaize, Inc. (www.blaize.com) is a SoC designer and manufacturer
> with integrated programmable Graph-Streaming-Processors for AI
> and ML. This series adds support for the Blaize BLZP1600 SoC.
>
> The SoC can run as either a PCIe based accelerator in a host
> system, or as a stand alone SoC running Linux on its integrated
> dual core ARM Cortex A53 cluster.
>
> The SoC includes a suite of peripherals, support for which will
> be added later.
>
> This first series is just the basics to get the upstream
> kernel to boot with a UART console and ARM SCMI based
> clocks and resets.
>
Hi Niko,
This version looks good to me, but it's likely that others
still have review comments. Either way I should let you know
of the next steps for merging the series.
Since the 6.13 development cycle is now over (the
merge window starts once Linus publishes 6.12
this weekend), the earliest release to merge this
into is now 6.14.
Once 6.13-rc1 is out and the patch review is complete,
you can submit the patches for inclusion by sending
to:soc@...ts.linux.dev (formerly soc@...nel.org).
This is usually done as a pull request, but separate
patches are fine as well, especially if you don't yet
have a kernel.org account.
After the entry to the MAINTAINERS file is merged,
I suggest you also apply for a kernel.org account,
see [1]. You probably also read the documentation at
[2] about the usual process, let me know if you
have questions about that.
Arnd
[1] https://korg.docs.kernel.org/accounts.html
[2] https://www.kernel.org/doc/Documentation/process/maintainer-soc.rst
Powered by blists - more mailing lists