From: Jakob Unterwurzacher <jakob.unterwurzacher@cherry.de>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Quentin Schulz <quentin.schulz@cherry.de>,
Jakob Unterwurzacher <jakobunt@gmail.com>
Cc: stable@vger.kernel.org, Heiko Stuebner <heiko.stuebner@cherry.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: fix emmc reset polarity on px30-cobra
Date: Tue, 9 Jun 2026 10:10:41 +0200 [thread overview]
Message-ID: <907fc663-6ccd-4bf7-906c-04f8603a692d@cherry.de> (raw)
In-Reply-To: <3631825.d7IHhHJzqS@phil>
On 6/2/26 23:08, Heiko Stuebner wrote:
>
> as Quentin remarked, author (@gmail) and signed-off-by do not match.
> While I'm generally open to fixing things, when it touches the DCO this
> isn't the case.
>
> So please resend this with the correct author.
>
> In general "git send-email" will do the correct thing (that From: line),
> when patch author and email-id do not match.
For posterity:
What seems to be happening is that Gmail rewrites the "From: " header on
the server side. git send-email does now know this, so doesn't add the
extra "From: " line.
Making the final "From: " explicit in .gitconfig using
[sendemail]
from = Jakob Unterwurzacher <jakobunt@gmail.com>
now makes git send-email add that extra "From: " line in the email body
as expected.
I'll resend the patch now.
Thanks, Jakob
prev parent reply other threads:[~2026-06-09 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 9:22 [PATCH] arm64: dts: rockchip: fix emmc reset polarity on px30-cobra Jakob Unterwurzacher
2026-05-12 10:47 ` Quentin Schulz
2026-06-02 21:08 ` Heiko Stuebner
2026-06-09 8:10 ` Jakob Unterwurzacher [this message]
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=907fc663-6ccd-4bf7-906c-04f8603a692d@cherry.de \
--to=jakob.unterwurzacher@cherry.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=jakobunt@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=stable@vger.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