Linux SOC development
 help / color / mirror / Atom feed
From: Matt Redfearn <matt.redfearn@blaize.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	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 11:22:15 +0000	[thread overview]
Message-ID: <ac96f306-e5ea-4514-b25d-18b44777d3e6@blaize.com> (raw)
In-Reply-To: <h5awakp52e6pxnnfrclhtlhhs3i66twvmqwlf5vmnfwk2xhbwr@marp6wti72ti>


On 05/12/2024 08:16, Krzysztof Kozlowski wrote:
> On Wed, Dec 04, 2024 at 04:05:29PM +0000, Nikolaos Pasaloukos wrote:
>> Add MAINTAINERS entry for Blaize SoC platform with a list of
>> maintainers.
>>
>> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
>> ---
>>   MAINTAINERS | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 273a84483b74543b510de7b08804bbd1f6514358..43846a23f9d990ae9fe066e65ed2bdd36376e327 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2238,6 +2238,15 @@ F:	arch/arm64/boot/dts/bitmain/
>>   F:	drivers/clk/clk-bm1880.c
>>   F:	drivers/pinctrl/pinctrl-bm1880.c
>>   
>> +ARM/BLAIZE ARCHITECTURE
>> +M:	James Cowgill <james.cowgill@blaize.com>
>> +M:	Matt Redfearn <matt.redfearn@blaize.com>
>> +M:	Neil Jones <neil.jones@blaize.com>
>> +M:	Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> Just to be clear: this is list of active maintainers, so all above are
> supposed to perform reviews or maintainer duties. This is not
> credits/managers/I-need-to-please-someone list.

Hi Krzysztof,

Yes, I will be an active maintainer of the board upstream.

>
> With the assumption these are active maintainers:
>
> 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?

Thanks,

Matt


>
> Best regards,
> Krzysztof
>

  reply	other threads:[~2024-12-05 11:28 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 [this message]
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 ` [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=ac96f306-e5ea-4514-b25d-18b44777d3e6@blaize.com \
    --to=matt.redfearn@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=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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