From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matt Redfearn <matt.redfearn@blaize.com>,
Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [PATCH v5 6/6] MAINTAINER: Add entry for Blaize SoC
Date: Thu, 5 Dec 2024 13:12:46 +0100 [thread overview]
Message-ID: <6999aff2-5889-4786-9395-28d9ce40f6c0@kernel.org> (raw)
In-Reply-To: <ac96f306-e5ea-4514-b25d-18b44777d3e6@blaize.com>
On 05/12/2024 12:22, Matt Redfearn wrote:
>>
>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> They should also ack it to confirm they understand the burden.
>
> Acked-by: Matt Redfearn <matt.redfearn@blaize.com>
>
>
> A question about process: should Niko resend V5 with all of the acks?
Normally not, here however after finished review expectation was to send
it to soc tree (I think Arnd described the process).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-05 12:12 UTC|newest]
Thread overview: 14+ 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 [this message]
2024-12-05 14:35 ` James Cowgill
2024-12-05 14:39 ` Neil Jones
2024-12-13 17:00 ` [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC patchwork-bot+linux-soc
-- strict thread matches above, loose matches on Subject: below --
2024-11-15 14:58 Niko Pasaloukos
2024-11-15 14:58 ` [PATCH v5 6/6] MAINTAINER: Add entry for Blaize SoC Niko 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=6999aff2-5889-4786-9395-28d9ce40f6c0@kernel.org \
--to=krzk@kernel.org \
--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=matt.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=nikolaos.pasaloukos@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