From: "Christian König" <christian.koenig@amd.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
tursulin@ursulin.net
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix incorrect RCU teardown order
Date: Tue, 22 Sep 2026 11:44:22 +0200 [thread overview]
Message-ID: <026cf5c2-585d-4171-b27f-74cd01e81b02@amd.com> (raw)
In-Reply-To: <87116b9512796cf3ac2db310aa320f94a87a96e4@intel.com>
On 9/22/26 11:31, Jani Nikula wrote:
> On Thu, 03 Sep 2026, "Christian König" <ckoenig.leichtzumerken@gmail.com> wrote:
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>
> Christian, this was already merged, but it's flagged by checkpatch with
> From/Signed-off-by mismatch. I see that you've sent a bunch of patches
> like this recently. Please configure git to add the same From: as your
> Signed-off-by, or set the Signed-off-by to your From.
>
> Though I don't understand how e.g. commit 643f9c6d862e ("MAINTAINERS:
> change TTM maintainers to Natalie and Arun") got the AMD address as
> author, even though the patch has gmail [1].
Yeah, that is my normal setup for the last 15 years :(
AMDs mail servers do very very strange things to mails, including converting text mail to HTML, mangling mails so that patches won't apply any more, changing the encoding from utf-8 to something else because non latin letter in my last name etc....
Because of that I have an exception from my manager to use my gmail account to send patches with a "Reply-To: christian.koenig@amd.com" in the header.
I could fight AMDs IT to get an exception for the email setup, but that has been a very time consuming task for other so I have never done that.
Regards,
Christian.
>
>
> BR,
> Jani.
>
>
> [1] https://lore.kernel.org/all/20260915154804.605772-1-christian.koenig@amd.com/
>
next prev parent reply other threads:[~2026-09-22 9:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:36 [PATCH] drm/i915: fix incorrect RCU teardown order Christian König
2026-09-03 13:42 ` ✗ i915.CI.BAT: failure for " Patchwork
2026-09-07 9:54 ` [PATCH] " Tvrtko Ursulin
2026-09-07 11:53 ` Christian König
2026-09-08 7:25 ` Tvrtko Ursulin
2026-09-09 7:24 ` Christian König
2026-09-16 9:51 ` Tvrtko Ursulin
2026-09-16 12:53 ` Christian König
2026-09-17 7:59 ` Tvrtko Ursulin
2026-09-07 12:15 ` ✓ i915.CI.BAT: success for drm/i915: fix incorrect RCU teardown order (rev2) Patchwork
2026-09-07 18:35 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-16 14:47 ` ✓ i915.CI.BAT: success for drm/i915: fix incorrect RCU teardown order (rev3) Patchwork
2026-09-16 21:19 ` ✓ i915.CI.Full: " Patchwork
2026-09-22 9:31 ` [PATCH] drm/i915: fix incorrect RCU teardown order Jani Nikula
2026-09-22 9:44 ` Christian König [this message]
2026-09-22 10:15 ` Jani Nikula
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=026cf5c2-585d-4171-b27f-74cd01e81b02@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
/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