intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [GIT PULL] GVT-g fixes for 4.11 merge
Date: Tue, 07 Feb 2017 16:50:28 +0200	[thread overview]
Message-ID: <87o9yeukaz.fsf@intel.com> (raw)
In-Reply-To: <20170207100745.2542xdvqb5rb7p43@zhen-hp.sh.intel.com>

On Tue, 07 Feb 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> These are GVT-g changes for 4.11 merge window, mostly for gvt init
> order fix that impacted resource handling for device model, the one
> i915 change has been reviewed and acked.
>
> I can't find good tag on dinf for this now, so base on current dinf.
> I can re-generate as required.

This is fine for dinf. Pulled, thanks.

BR,
Jani.


>
> thanks
> ---
>
> The following changes since commit 18566acac18f5784347bc5fe636a26897d1c963b:
>
>   Merge branch 'exynos-drm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next (2017-02-01 08:43:42 +1000)
>
> are available in the git repository at:
>
>   https://github.com/01org/gvt-linux.git tags/gvt-next-2017-02-07
>
> for you to fetch changes up to 2d6ceb8e654a0ce998762b13f0ba2c275220a244:
>
>   drm/i915/gvt: fix vgpu type size init (2017-02-07 17:22:01 +0800)
>
> ----------------------------------------------------------------
> Chuanxiao Dong (1):
>       drm/i915/gvt: add more resolutions in virtual edid
>
> Zhenyu Wang (5):
>       drm/i915: make intel_gvt_init() later instead of too early
>       drm/i915/gvt: move intel iommu detection to intel_gvt_init()
>       drm/i915/gvt: remove detect_host() MPT hook
>       drm/i915/gvt: use normal mmio read function for firmware exposure
>       drm/i915/gvt: fix vgpu type size init
>
>  drivers/gpu/drm/i915/gvt/display.c   | 19 +++++++++------
>  drivers/gpu/drm/i915/gvt/firmware.c  | 47 +++---------------------------------
>  drivers/gpu/drm/i915/gvt/gvt.c       | 14 +++++------
>  drivers/gpu/drm/i915/gvt/hypercall.h |  1 -
>  drivers/gpu/drm/i915/gvt/kvmgt.c     | 38 -----------------------------
>  drivers/gpu/drm/i915/gvt/mpt.h       | 12 ---------
>  drivers/gpu/drm/i915/gvt/vgpu.c      | 13 +++++-----
>  drivers/gpu/drm/i915/i915_drv.c      | 14 +++++------
>  drivers/gpu/drm/i915/intel_gvt.c     |  5 ++++
>  9 files changed, 42 insertions(+), 121 deletions(-)

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-02-07 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 10:07 [GIT PULL] GVT-g fixes for 4.11 merge Zhenyu Wang
2017-02-07 14:50 ` Jani Nikula [this message]

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=87o9yeukaz.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=zhenyuw@linux.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;
as well as URLs for NNTP newsgroup(s).