From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"King, Colin" <colin.king@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"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: Wed, 17 Aug 2022 22:34:59 +0100 [thread overview]
Message-ID: <9f6e3433-5748-b7e4-bbc6-b0e47cb9d1c5@gmail.com> (raw)
In-Reply-To: <116bdd80d399da39a6ba3f3d2f71a1f78e2b026f.camel@intel.com>
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:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Here's one gvt-fixes pull for 6.0-rc. Major one is Cometlake
>>>>> regression
>>>>> fix for mmio table rework, and others are left kernel doc fixes
>>>>> not pushed yet.
>>>>>
>>>>> Thanks
>>>>> --
>>>>> The following changes since commit
>>>>> a7a47a5dfa9a9692a41764ee9ab4054f12924a42:
>>>>>
>>>>> drm/i915/reset: Add additional steps for Wa_22011802037 for
>>>>> execlist backend (2022-07-25 15:57:54 +0100)
>>>>>
>>>>> are available in the Git repository at:
>>>>>
>>>>> https://github.com/intel/gvt-linux.git tags/gvt-fixes-2022-
>>>>> 08-15
>>>>>
>>>>> for you to fetch changes up to
>>>>> 394f0560a76298842defd1d95bd64b203a5fdcc4:
>>>>>
>>>>> drm/i915/gvt: Fix Comet Lake (2022-08-15 10:54:03 +0800)
>>>>>
>>>>> ---------------------------------------------------------------
>>>>> -
>>>>> gvt-fixes-2022-08-15
>>>>>
>>>>> - CometLake regression fix in mmio table rework (Alex)
>>>>> - misc kernel doc and typo fixes
>>>>>
>>>>> ---------------------------------------------------------------
>>>>> -
>>>>> Alex Williamson (1):
>>>>> drm/i915/gvt: Fix Comet Lake
>>>>>
>>>>> Colin Ian King (1):
>>>>> drm/i915/reg: Fix spelling mistake "Unsupport" ->
>>>>> "Unsupported"
>>>>
>>>> dim: d6632370536d ("drm/i915/reg: Fix spelling mistake
>>>> "Unsupport" -> "Unsupported""): committer Signed-off-by missing.
>>>>
>>>> is it possible to fix this in your tree?
>>>
>>> Sorry about that. Let me re-generate.
>>
>> 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.
Colin
>
> Thanks,
> Rodrigo.
>
>>
>> So maybe I can't change that?
>>
>>
>
next prev parent reply other threads:[~2022-08-19 12:23 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) [this message]
2022-08-18 10:15 ` Jani Nikula
2022-08-18 14:27 ` Jani Nikula
2022-08-18 15:43 ` Vivi, Rodrigo
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 ` [Intel-gfx] " Zhenyu Wang
2019-11-12 6:18 Zhenyu Wang
2019-11-12 6:18 ` [Intel-gfx] " Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-11-12 20:36 ` [Intel-gfx] " 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=9f6e3433-5748-b7e4-bbc6-b0e47cb9d1c5@gmail.com \
--to=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=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox