Re: [Intel-gfx] [GIT PULL] GVT next changes for drm-intel-next-queued

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Tue, Jan 11, 2022 at 06:08:28AM -0500, Wang, Zhi A wrote:
> On 1/11/22 6:08 AM, Wang, Zhi A wrote:
> > On 1/11/2022 12:52 AM, Vivi, Rodrigo wrote:
> >> On Fri, 2022-01-07 at 14:43 +0000, Wang, Zhi A wrote:
> >>> Hi folks:
> >>>
> >>> Happy holidays! This pull mostly contains the code re-factors patches
> >>> from Guenter Roeck and Rikard. Also a minor change from Zhenyu.
> >>>
> >>> Zhi
> >>>
> >>> The following changes since commit
> >>> 3bfa7d40ce736ffbbfe07127061f54b359ee2b12:
> >>>
> >>>     drm/i915/dg2: Add support for new DG2-G11 revid 0x5 (2021-08-06
> >>> 09:03:10 -0700)
> >>>
> >>> are available in the Git repository at:
> >>>
> >>>     https://github.com/intel/gvt-linux tags/gvt-next-2022-01-07
> >>>
> >>> for you to fetch changes up to
> >>> d7a8585430f2b6df5960bbc305edcec5a55180f3:
> >> I'm not sure what's going on here, but:
> >>
> >> dim: no pull request found
> >>
> >> did you do anything different on this round for generating and sending
> >> out this pull request email?
> > Strange.
> >
> > I generated this pull request by git pull-request since there is no
> > support for generating pull-request for gvt-next right in dim now. Can
> > you share me the command line of dim you were using for apply this pull
> > request? I can try to apply it before sending the pull request.
> >
> > Thanks,
> >
> > Zhi.
> >
> Hi Vivi:
> 
> I did some checks and dumped the plain source of the email I sent. I
> guess I figured out the reason. It's the problem of thunderbird in
> Windows. When it sends the plain email, it will replace some space with
> "Â", which caused the dim cannot find the git repo url. I have no idea
> how that can happen since Thunderbird in Linux worked totally fine with
> the same settings.
> 
> Before the vacation, my VPN certificate in Linux has been expired. I had
> to use the thunderbird in Windows, which caused the problem above.
> 
> Will re-sent. Sorry for the bumps.

understood. no problem at all. it happens.

Thanks for resending, but there's something else now...

dim attempt a mega rebase of thousands and thousands of patches
when trying to apply this.

Could you please rebase on a more recent drm-intel-next tag?

Thanks,
Rodrigo.

> 
> Zhi.
> 
> >>>     drm/i915/gvt: Constify vgpu_types (2021-12-16 09:13:02 -0500)
> >>>
> >>> ----------------------------------------------------------------
> >>> Guenter Roeck (1):
> >>>         drm/i915/gvt: Use list_entry to access list members
> >>>
> >>> Rikard Falkeborn (9):
> >>>         drm/i915/gvt: Constify intel_gvt_gtt_gma_ops
> >>>         drm/i915/gvt: Constify intel_gvt_gtt_pte_ops
> >>>         drm/i915/gvt: Constify intel_gvt_irq_ops
> >>>         drm/i915/gvt: Constify intel_gvt_sched_policy_ops
> >>>         drm/i915/gvt: Constify gvt_mmio_block
> >>>         drm/i915/gvt: Constify cmd_interrupt_events
> >>>         drm/i915/gvt: Constify formats
> >>>         drm/i915/gvt: Constify gtt_type_table_entry
> >>>         drm/i915/gvt: Constify vgpu_types
> >>>
> >>> Zhenyu Wang (1):
> >>>         drm/i915/gvt: Fix cmd parser error for Passmark9
> >>>
> >>>    drivers/gpu/drm/i915/gvt/cmd_parser.c   |  2 +-
> >>>    drivers/gpu/drm/i915/gvt/dmabuf.c       | 18 +++------
> >>>    drivers/gpu/drm/i915/gvt/fb_decoder.c   | 24 ++++++------
> >>>    drivers/gpu/drm/i915/gvt/gtt.c          | 68
> >>> ++++++++++++++++-----------------
> >>>    drivers/gpu/drm/i915/gvt/gtt.h          |  4 +-
> >>>    drivers/gpu/drm/i915/gvt/gvt.h          |  2 +-
> >>>    drivers/gpu/drm/i915/gvt/handlers.c     | 13 ++++---
> >>>    drivers/gpu/drm/i915/gvt/interrupt.c    | 10 ++---
> >>>    drivers/gpu/drm/i915/gvt/interrupt.h    |  2 +-
> >>>    drivers/gpu/drm/i915/gvt/sched_policy.c |  2 +-
> >>>    drivers/gpu/drm/i915/gvt/scheduler.h    |  2 +-
> >>>    drivers/gpu/drm/i915/gvt/vgpu.c         |  4 +-
> >>>    12 files changed, 72 insertions(+), 79 deletions(-)
> >>>
> >
>