From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-next for 4.21
Date: Tue, 11 Dec 2018 10:20:28 +0800 [thread overview]
Message-ID: <20181211022028.GC32123@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20181211004124.GD35729@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 3140 bytes --]
On 2018.12.10 16:41:24 -0800, Rodrigo Vivi wrote:
>
> On Fri, Dec 07, 2018 at 12:36:59PM +0800, Zhenyu Wang wrote:
> >
> > Hi,
> >
> > As I was hoping to possibly merge more new stuff for next kernel e.g
> > CFL support, etc, but seems those're still not stable enough so better
> > wait for next cycle, so sorry for the late.
>
> If I understood correctly Jani already sent the latest pull request
> targeting 4.21. Right Jani?
>
> Should we start queueing this for 4.22?
>
yeah, sorry I missed that window, but this one actually contains stuff
for -next-fixes besides typo fixes, otherwise 4.21 will be problematic.
Let me generate another one for dinf.
thanks
> >
> > This includes mostly one regression fix for drm-intel-next when we
> > introduced during previous shadow ctx ppgtt failure fix patch, and one
> > update on force-to-nonpriv register list. There're also three typo
> > fixes we received, I think they're trivial so should be no harm to
> > include.
> >
> > Thanks
> > --
> > The following changes since commit 4377d4e0d3d511986033ba7b4182d5a80b7f9ea2:
> >
> > drm/i915: Update DRIVER_DATE to 20181204 (2018-12-04 19:26:17 +0200)
> >
> > are available in the Git repository at:
> >
> > https://github.com/intel/gvt-linux.git tags/gvt-next-2018-12-07
> >
> > for you to fetch changes up to d1810909d841314ba94b14dc3de9e9fbc13b046a:
> >
> > drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts" (2018-12-07 12:01:09 +0800)
> >
> > ----------------------------------------------------------------
> > gvt-next-2018-12-07
> >
> > - Fix -next regression on shadow ctx's ppgtt destroy (Xiong)
> > - Update force-to-nonpriv register list (Yan)
> > - three typo fixes
> >
> > ----------------------------------------------------------------
> > Colin Ian King (1):
> > drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts"
> >
> > Peng Hao (1):
> > drm/i915/gvt: fix a typo: "registeration" -> "registration".
> >
> > Xinyun Liu (1):
> > drm/i915/gvt: fix typo in two MI cmd annotation
> >
> > Xiong Zhang (1):
> > drm/i915/gvt: Fix shadow ctx ppgtt destroy function
> >
> > Zhao Yan (1):
> > drm/i915/gvt: update force-to-nonpriv register whitelist
> >
> > drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
> > drivers/gpu/drm/i915/gvt/gvt.c | 2 +-
> > drivers/gpu/drm/i915/gvt/gvt.h | 4 ++++
> > drivers/gpu/drm/i915/gvt/handlers.c | 1 +
> > drivers/gpu/drm/i915/gvt/interrupt.c | 2 +-
> > drivers/gpu/drm/i915/gvt/scheduler.c | 33 +++++++++++++++++++++++++++++++++
> > 6 files changed, 43 insertions(+), 5 deletions(-)
> >
> > --
> > Open Source Technology Center, Intel ltd.
> >
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>
>
>
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-11 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 4:36 [PULL] gvt-next for 4.21 Zhenyu Wang
2018-12-11 0:41 ` Rodrigo Vivi
2018-12-11 2:20 ` Zhenyu Wang [this message]
2018-12-11 10:02 ` Jani Nikula
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=20181211022028.GC32123@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=hang.yuan@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=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