public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	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>, Arnd Bergmann <arnd@arndb.de>,
	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 1/6] dt-bindings: Add Blaize vendor prefix
Date: Tue, 19 Nov 2024 13:33:28 +0000	[thread overview]
Message-ID: <bc471aeb-e9fd-4aa9-9bcc-a59d3c2e47b8@blaize.com> (raw)
In-Reply-To: <c1885e24-8051-4c91-9870-18eb4218a2ff@kernel.org>

On 19/11/2024 13:05, Krzysztof Kozlowski wrote:
> On 15/11/2024 15:58, Niko Pasaloukos wrote:
>> Blaize, Inc. (www.blaize.com) is a SoC manufacturer with integrated
>> programmable Graph-Streaming-Processors for AI and ML.
>>
>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> Here and in all other patches - you still have the same checkpatch
> warning I asked to fix.
>
>
> git format-patch -6 -v5
> scripts/checkpatch.pl v5*
>
> Your SoB does not match From. This MUST be fixed.
>
> Best regards,
> Krzysztof

Hi Krzysztof,

Just to be certain and fix it properly, do you mean that the issue that you
are talking about is that the 'From' appears as 'Niko Pasaloukos' and I am
signing with SoB as 'Nikolaos Pasaloukos'?
I'm really sorry, if that's the case, I will fix it and yes, there must be
a misconfiguration on my system. Would I need to prepare a v6 for this?
If it is not that, then I am really sorry but I will need more information.

Best regards,
Nikolaos Pasaloukos


  reply	other threads:[~2024-11-19 13:34 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 [this message]
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 3/6] arm64: Add Blaize BLZP1600 SoC family Niko Pasaloukos
2024-11-19 13:03   ` Krzysztof Kozlowski
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 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
  -- strict thread matches above, loose matches on Subject: below --
2024-12-04 16:05 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

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=bc471aeb-e9fd-4aa9-9bcc-a59d3c2e47b8@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=krzk@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