From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Olof Johansson <olof@lixom.net>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"soc@lists.linux.dev" <soc@lists.linux.dev>
Subject: Re: [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC
Date: Tue, 19 Nov 2024 12:47:44 +0000 [thread overview]
Message-ID: <0c3063f2-1a5d-4ada-a813-7e18a681510e@blaize.com> (raw)
In-Reply-To: <141c7d39-9f0e-4c1c-86c5-149328ab979a@app.fastmail.com>
On 15/11/2024 15:09, Arnd Bergmann wrote:
> On Fri, Nov 15, 2024, at 15:58, Niko Pasaloukos wrote:
>> Blaize, Inc. (http://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@lists.linux.dev (formerly soc@kernel.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://urldefense.com/v3/__https://korg.docs.kernel.org/accounts.html__;!!FddXBOku!ny-gN1hGaRTxNpi1ADJf_s3xLmuIdAZzGy4uj6kacOw-p3lLhZfSFLF2Mb9UcuIbd1By_ERGVnHqEbEiXhbK1g$
> [2] https://urldefense.com/v3/__https://www.kernel.org/doc/Documentation/process/maintainer-soc.rst__;!!FddXBOku!ny-gN1hGaRTxNpi1ADJf_s3xLmuIdAZzGy4uj6kacOw-p3lLhZfSFLF2Mb9UcuIbd1By_ERGVnHqEbHSKH7PdA$
Hi Arnd,
Thank you very much for the detailed explanation of the merging process and release
cycles.
Also, I would like to thank all the people who help me during the review process
and for their helpful comments.
Best regards,
Niko
next prev parent reply other threads:[~2024-11-19 12:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 14:58 [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-15 14:58 ` [PATCH v5 1/6] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2024-11-19 13:05 ` Krzysztof Kozlowski
2024-11-19 13:33 ` Nikolaos Pasaloukos
2024-11-19 13:37 ` Krzysztof Kozlowski
2024-11-19 15:23 ` Nikolaos Pasaloukos
2024-11-19 15:52 ` Krzysztof Kozlowski
2024-11-19 16:23 ` Nikolaos Pasaloukos
2024-11-15 14:58 ` [PATCH v5 2/6] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-19 13:00 ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 3/6] arm64: Add Blaize BLZP1600 SoC family Niko Pasaloukos
2024-11-19 13:03 ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 4/6] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2024-11-19 13:02 ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 5/6] arm64: defconfig: Enable Blaize BLZP1600 platform Niko Pasaloukos
2024-11-19 13:03 ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 6/6] MAINTAINER: Add entry for Blaize SoC Niko Pasaloukos
2024-11-15 15:09 ` [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Arnd Bergmann
2024-11-19 12:47 ` Nikolaos Pasaloukos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 16:05 Nikolaos Pasaloukos via B4 Relay
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=0c3063f2-1a5d-4ada-a813-7e18a681510e@blaize.com \
--to=nikolaos.pasaloukos@blaize.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=soc@lists.linux.dev \
--cc=will@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