From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexander Koskovich <AKoskovich@pm.me>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: display: panel: Document Tianma TA066VVHM03
Date: Mon, 9 Mar 2026 08:54:38 +0100 [thread overview]
Message-ID: <2d1d5c7c-61b1-4f5a-b039-02ceb2a02c1a@kernel.org> (raw)
In-Reply-To: <PU91d8ChpHqZx-aqR57qt-3XBGBOl_oCbF0SSI_q3uGK9UXUUWplDdDD4m_OGbpXn3Ayx0DCy0wHYe5-nuZeZc-Xy_77mvHl17KrTJcPt-w=@pm.me>
On 09/03/2026 08:41, Alexander Koskovich wrote:
> On Monday, March 9th, 2026 at 3:35 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> BTW, all of your patches have mismatched From and SoB cases. It passes
>> the checks but I do not see reason why different case should be used.
>> Especially that it is manual process to achieve that - none of the
>> standard ways of using git produce such result, because SoB is added
>> automatically based on From name. Unless your mail server is changing
>> these, but that's also odd.
>>
>> This should be fixed in all of your patches, IMO.
>
> I did notice that, looked into it briefly the other day and it appears to be Protonmail Bridge that is doing it, I always use "akoskovich@pm.me", but Protonmail seems to be sending out as "AKoskovich@pm.me".
>
> It also made some linux-media CI checks fail :(
>
> Would you suggest I change my git identity to use uppercase here and then resend all patches?
>
Just change it in Proton settings to lowercase. Or don't use Proton for
kernel development - in the past it was causing a lot of troubles, so
here we have another reason - mangling silently with headers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-09 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 21:08 [PATCH v2 0/2] Add support for Tianma TA066VVHM03 DSI panel Alexander Koskovich
2026-03-08 21:09 ` [PATCH v2 1/2] dt-bindings: display: panel: Document Tianma TA066VVHM03 Alexander Koskovich
2026-03-09 7:35 ` Krzysztof Kozlowski
2026-03-09 7:41 ` Alexander Koskovich
2026-03-09 7:54 ` Krzysztof Kozlowski [this message]
2026-03-09 7:59 ` Alexander Koskovich
2026-03-10 2:50 ` Claude review: " Claude Code Review Bot
2026-03-08 21:09 ` [PATCH v2 2/2] drm/panel: Add support for Tianma TA066VVHM03 panel Alexander Koskovich
2026-03-10 2:50 ` Claude review: " Claude Code Review Bot
2026-03-10 2:50 ` Claude review: Add support for Tianma TA066VVHM03 DSI panel Claude Code Review Bot
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=2d1d5c7c-61b1-4f5a-b039-02ceb2a02c1a@kernel.org \
--to=krzk@kernel.org \
--cc=AKoskovich@pm.me \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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