On 2017.12.21 19:07:07 -0800, Rodrigo Vivi wrote: > On Fri, Dec 22, 2017 at 02:43:06AM +0000, Zhenyu Wang wrote: > > > > Hi, > > > > Here's last gvt-next pull for 4.16 merge window. I need to backmerge > > once for one i915 param change to resolve patch dependence. This includes > > mmio switch optimization, cleanups for write protect handler and our > > i915_reg_t vs. offset usage. > > > > thanks > > -- > > The following changes since commit ee5b5bf351ec8cd8f11c631cb76b30f602e866ee: > > > > drm/i915: Update DRIVER_DATE to 20171214 (2017-12-14 12:10:02 -0800) > > > > are available in the Git repository at: > > > > https://github.com/intel/gvt-linux.git tags/gvt-next-2017-12-22 > > > > for you to fetch changes up to 6660c07ab5d3a1388b07af55b2503dd7b2cc61f7: > > > > drm/i915/gvt: move write protect handler out of mmio emulation function (2017-12-21 11:03:27 +0800) > > > > ---------------------------------------------------------------- > > gvt-next-2017-12-22: > > > > - more mmio switch optimization (Weinan) > > - cleanup i915_reg_t vs. offset usage (Zhenyu) > > - move write protect handler out of mmio handler (Zhenyu) > > > > ---------------------------------------------------------------- > > Weinan Li (4): > > drm/i915/gvt: refine trace_render_mmio > > drm/i915/gvt: optimize for vGPU mmio switch > > drm/i915/gvt: refine mocs save restore policy > > drm/i915/gvt: load host render mocs once in mocs switch > > > > Xiaolin Zhang (1): > > drm/i915/gvt: Fix pipe A enable as default for vgpu > > > > Zhenyu Wang (4): > > Merge tag 'drm-intel-next-2017-12-14' into gvt-next > > drm/i915/gvt: always use i915_reg_t for MMIO handler definition > > drm/i915/gvt: cleanup usage for typed mmio reg vs. offset > > drm/i915/gvt: move write protect handler out of mmio emulation function > > dim apply-pull drm-intel-next-queued > > https://github.com/intel/gvt-linux.git tags/gvt-next-2017-12-22 > From https://github.com/intel/gvt-linux > * tag gvt-next-2017-12-22 -> FETCH_HEAD > dim: ERROR: 6660c07ab5d3a1388b07af55b2503dd7b2cc61f7 is lacking mandatory review, aborting > Looks dim doesn't allow committer == author without ack or r-b? Is this really mandatory required? If yes, I will apply this rule for gvt tree as well and encourage gvt developer to send a-b/r-b mail as looks people more like to use IM to exchange review comment.. -- Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
