[Intel-gfx] [PULL] gvt-fixes

[Vivi, Rodrigo]

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)

Thanks,
Rodrigo.

> 
> So maybe I can't change that?
> 
>