public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>,
	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 16:52:15 +0100	[thread overview]
Message-ID: <38c2c941-42e1-4d7c-aaa2-3c11dcea4e05@kernel.org> (raw)
In-Reply-To: <09170fdb-018a-401e-a186-ccd0f5e993d8@blaize.com>

On 19/11/2024 16:23, Nikolaos Pasaloukos wrote:
> Hi Krzysztof,
> 
> That's a very tricky error to pick it up. `checkpatch` on my end doesn't produce
> an error. The header file on my patches starts as:
> 'From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>'
> I had set the mail account as Forname: Nikolaos, Surname: Pasaloukos and
> preferred name as Niko. It is an Outlook365 issue I think.
> 
> That said, when I was trying to send my patches, the mail server was converting
> my name 'Nikolaos Pasaloukos' to the preferred name 'Niko Pasaloukos'.

Usually it is not a problem to commit patches with one name and send
with other - git send-email will properly add two From headers like:
https://lore.kernel.org/all/20241119154245.442961-4-pablo@netfilter.org/

If your git history has correct From matching SoB, then indeed
checkpatch on your end will not complain.

If that is the case, it means your SMTP server *rewrites* the From
header. Not nice... but what to expect from Microsoft? They learnt open
source just recently and before open source was communism for them...

You can change your local name to match whatever Microsoft wants to set
or you can use b4 relay to send the patches.

https://b4.docs.kernel.org/en/latest/contributor/send.html

> 
> Do I need to resend v5 again after this is fixed, having applied all the
> additional Reviewed-by? What would be my next step here?

Yes, please resend a v5 with tags applied and fixed problem with From/SoB.


Best regards,
Krzysztof

  reply	other threads:[~2024-11-19 15:52 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 [this message]
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
  -- 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=38c2c941-42e1-4d7c-aaa2-3c11dcea4e05@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=matthew.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