All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
	"colin.i.king@gmail.com" <colin.i.king@gmail.com>,
	"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
	"King, Colin" <colin.king@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"intel-gvt-dev@lists.freedesktop.org"
	<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-fixes
Date: Thu, 18 Aug 2022 15:43:32 +0000	[thread overview]
Message-ID: <bc33d83b5dd01bddd96ec787fa2b948a04cdd3b5.camel@intel.com> (raw)
In-Reply-To: <87wnb5ocdl.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2795 bytes --]

On Thu, 2022-08-18 at 17:27 +0300, Jani Nikula wrote:
On Thu, 18 Aug 2022, Jani Nikula <jani.nikula@intel.com<mailto:jani.nikula@intel.com>> wrote:
On Wed, 17 Aug 2022, "Colin King (gmail)" <colin.i.king@gmail.com<mailto:colin.i.king@gmail.com>> wrote:
On 17/08/2022 21:07, Vivi, Rodrigo wrote:
On Tue, 2022-08-16 at 12:43 +0800, Zhenyu Wang wrote:
On 2022.08.16 12:05:08 +0800, Zhenyu Wang wrote:
On 2022.08.15 19:32:45 -0400, Rodrigo Vivi wrote:
On Mon, Aug 15, 2022 at 10:38:55AM +0800, Zhenyu Wang wrote:
oh, surprise! I just found Colin's email is actually defined in
.mailmap,
so all his commits in kernel are changed for @intel.com address as in
mailmap...

Colin, would you mind to get the Sign-off-by in the patches the same
as your authorship so the tools don't get confused?
(starting with modifying in tree this already merged patch)

Since my patches are generally trivial janitorial fixed done in my spare
time I'm going to get the .mailmap changed to use my gmail email address
rather than my Intel one (since I don't do kernel work in my current role).

This should clean up the confusion. Apologies.

Everyone hold your horses.

I think our tooling should handle the mailmap stuff. The commit *is*
fine, it's just that the when we check it, we let mailmap alter it. We
should check the commit without mailmap modifications.

In this case, it's actually not about Colin's Signed-off-by or mailmap
at all! Like the error message from dim says, "committer Signed-off-by
missing". Committer, not author!

$ git show -s tags/gvt-fixes-2022-08-15^ --pretty=fuller
commit d6632370536d0b80be3bfc90dd67e1f693335a75
Author:     Colin Ian King <colin.king@intel.com<mailto:colin.king@intel.com>>
AuthorDate: Tue Mar 15 20:24:49 2022 +0000
Commit:     Zhenyu Wang <zhenyuw@linux.intel.com<mailto:zhenyuw@linux.intel.com>>
CommitDate: Mon Aug 15 10:51:15 2022 +0800

    drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"

    There is a spelling mistake in a gvt_vgpu_err error message. Fix it.

    Fixes: 695fbc08d80f ("drm/i915/gvt: replace the gvt_err with gvt_vgpu_err")
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com<mailto:colin.i.king@gmail.com>>
    Signed-off-by: Zhi Wang <zhi.a.wang@intel.com<mailto:zhi.a.wang@intel.com>>
    Link: http://patchwork.freedesktop.org/patch/msgid/20220315202449.2952845-1-colin.i.king@gmail.com
    Reviewed-by: Zhi Wang <zhi.a.wang@intel.com<mailto:zhi.a.wang@intel.com>>

Committed by Zhenyu, Signed-off-by Zhi. Maybe caused by rebase by Zhenyu
after being committed by Zhi?

Probably easier if you could rebase it again signing it then?

I could bypass dim here, but this will likely affect someone else later in the upstream chain as well..


BR,
Jani.




[-- Attachment #2: Type: text/html, Size: 5394 bytes --]

  reply	other threads:[~2022-08-18 15:44 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  2:38 [Intel-gfx] [PULL] gvt-fixes Zhenyu Wang
2022-08-15 23:32 ` Rodrigo Vivi
2022-08-16  4:05   ` Zhenyu Wang
2022-08-16  4:43     ` Zhenyu Wang
2022-08-17 20:07       ` Vivi, Rodrigo
2022-08-17 21:34         ` Colin King (gmail)
2022-08-18 10:15           ` Jani Nikula
2022-08-18 14:27             ` Jani Nikula
2022-08-18 15:43               ` Vivi, Rodrigo [this message]
2022-08-22  3:00                 ` Zhenyu Wang
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  5:54 Zhenyu Wang
2023-08-02  7:17 ` Tvrtko Ursulin
2023-01-04  8:05 Zhenyu Wang
2023-01-04 11:34 ` Rodrigo Vivi
2023-01-05  0:15   ` Zhenyu Wang
2023-01-05 13:10     ` Rodrigo Vivi
2022-11-11  9:02 Zhenyu Wang
2022-11-22  5:11 ` Zhenyu Wang
2022-11-22  8:02   ` Tvrtko Ursulin
2022-07-11  5:20 Zhenyu Wang
2022-07-12 22:24 ` Rodrigo Vivi
2021-09-18  7:11 Zhenyu Wang
2021-09-27  9:39 ` Jani Nikula
2021-08-10  5:01 Zhenyu Wang
2021-08-10 13:52 ` Rodrigo Vivi
2021-07-15  2:22 Zhenyu Wang
2021-07-15 13:56 ` Rodrigo Vivi
2021-05-19  7:49 Zhenyu Wang
2021-05-19  8:50 ` Jani Nikula
2021-04-20  2:33 Zhenyu Wang
2021-04-20 13:43 ` Rodrigo Vivi
2021-01-08  4:59 Zhenyu Wang
2021-01-11 18:13 ` Jani Nikula
2020-11-17  2:39 Zhenyu Wang
2020-11-19  6:53 ` Rodrigo Vivi
2020-10-27  3:17 Zhenyu Wang
2020-10-27 20:46 ` Rodrigo Vivi
2020-10-28 11:18   ` Vivi, Rodrigo
2020-10-30  3:09     ` Zhenyu Wang
2020-10-30  5:21     ` Zhenyu Wang
2020-10-30 22:57       ` Vivi, Rodrigo
2020-09-17  6:42 Zhenyu Wang
2020-09-22 17:27 ` Jani Nikula
2020-06-17  4:34 Zhenyu Wang
2020-06-18 12:48 ` Joonas Lahtinen
2020-06-23  3:07   ` Zhenyu Wang
2020-06-29  8:18     ` Jani Nikula
2020-05-12  2:48 Zhenyu Wang
2020-05-12  7:00 ` Rodrigo Vivi
2020-04-14  8:36 Zhenyu Wang
2020-04-14 13:11 ` Rodrigo Vivi
2020-03-10  8:09 Zhenyu Wang
2020-03-10  9:33 ` Jani Nikula
2020-02-26 10:30 Zhenyu Wang
2020-02-26 22:00 ` Jani Nikula
2020-02-12  6:59 Zhenyu Wang
2020-02-12 14:54 ` Jani Nikula
2019-12-18  5:16 Zhenyu Wang
2019-12-18  9:20 ` Joonas Lahtinen
2019-11-22  3:33 Zhenyu Wang
2019-11-22  3:33 ` Zhenyu Wang
2019-11-12  6:18 Zhenyu Wang
2019-11-12  6:18 ` Zhenyu Wang
2019-11-12 20:36   ` Vivi, Rodrigo
2019-11-12 20:36     ` Vivi, Rodrigo

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=bc33d83b5dd01bddd96ec787fa2b948a04cdd3b5.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=colin.i.king@gmail.com \
    --cc=colin.king@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.