Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Nikolaos Pasaloukos via B4 Relay
	<devnull+nikolaos.pasaloukos.blaize.com@kernel.org>
Cc: soc@kernel.org
Subject: Re: [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC
Date: Fri, 13 Dec 2024 17:00:32 +0000	[thread overview]
Message-ID: <173410923224.3098520.11489875368543603546.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241204-blaize-blzp1600_init_board_support-v5-0-b642bcc49307@blaize.com>

Hello:

This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Wed, 04 Dec 2024 16:05:23 +0000 you 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.
> 
> [...]

Here is the summary with links:
  - [v5,1/6] dt-bindings: Add Blaize vendor prefix
    https://git.kernel.org/soc/soc/c/1fa9ce7e525d
  - [v5,2/6] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC
    https://git.kernel.org/soc/soc/c/f156403c2c8d
  - [v5,3/6] arm64: Add Blaize BLZP1600 SoC family
    https://git.kernel.org/soc/soc/c/c0b454a51755
  - [v5,4/6] arm64: dts: Add initial support for Blaize BLZP1600 CB2
    https://git.kernel.org/soc/soc/c/2e976f19d9c2
  - [v5,5/6] arm64: defconfig: Enable Blaize BLZP1600 platform
    https://git.kernel.org/soc/soc/c/b0837ce07980
  - [v5,6/6] MAINTAINER: Add entry for Blaize SoC
    https://git.kernel.org/soc/soc/c/d4c0d167b1f6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-12-13 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 16:05 [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 1/6] dt-bindings: Add Blaize vendor prefix Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 2/6] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 3/6] arm64: Add Blaize BLZP1600 SoC family Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 4/6] arm64: dts: Add initial support for Blaize BLZP1600 CB2 Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 5/6] arm64: defconfig: Enable Blaize BLZP1600 platform Nikolaos Pasaloukos via B4 Relay
2024-12-04 16:05 ` [PATCH v5 6/6] MAINTAINER: Add entry for Blaize SoC Nikolaos Pasaloukos via B4 Relay
2024-12-05  8:16   ` Krzysztof Kozlowski
2024-12-05 11:22     ` Matt Redfearn
2024-12-05 12:12       ` Krzysztof Kozlowski
2024-12-05 14:35     ` James Cowgill
2024-12-05 14:39     ` Neil Jones
2024-12-13 17:00 ` patchwork-bot+linux-soc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-15 14:58 [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-15 15:09 ` Arnd Bergmann
2024-11-19 12:47   ` Nikolaos Pasaloukos

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=173410923224.3098520.11489875368543603546.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=devnull+nikolaos.pasaloukos.blaize.com@kernel.org \
    --cc=soc@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