All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.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-fixes
Date: Wed, 3 Apr 2019 17:12:37 -0700	[thread overview]
Message-ID: <20190404001237.GA18158@intel.com> (raw)
In-Reply-To: <20190402094037.GB2322@zhen-hp.sh.intel.com>

On Tue, Apr 02, 2019 at 05:40:37PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-fixes for 5.1-rc4 which includes misc fixes for
> vGPU display plane size calculation, shadow mm pin count,
> error recovery path for workload create and one kerneldoc
> fix which I missed to include before.

dim: 000d38970e98 ("drm/i915/gvt: Correct the calculation of plane size"): Fixes: SHA1 needs at least 12 digits:
dim:     e546e281d33("drm/i915/gvt: Dmabuf support for GVT-g")
dim: ERROR: issues in commits detected, aborting

Is it something you could fix on your side without having
to by-pass dim this time?

Thanks,
Rodrigo.

> 
> Thanks.
> --
> The following changes since commit 26cdaac4793c49357d2c731f2190632cefb7efb1:
> 
>   drm/i915/icl: Fix VEBOX mismatch BUG_ON() (2019-03-28 15:36:40 +0200)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-04-02
> 
> for you to fetch changes up to a14f068545cc13db9e0ad0ea451ec42e5abc97c0:
> 
>   drm/i915/gvt: Fix kerneldoc typo for intel_vgpu_emulate_hotplug (2019-03-29 10:31:15 +0800)
> 
> ----------------------------------------------------------------
> gvt-fixes-2019-04-02
> 
> - Fix shadow mm pin count (Yan)
> - Fix cmd parser error path recover (Yan)
> - Fix vGPU display plane size calculation (Xiong)
> - Fix kerneldoc (Chris)
> 
> ----------------------------------------------------------------
> Chris Wilson (1):
>       drm/i915/gvt: Fix kerneldoc typo for intel_vgpu_emulate_hotplug
> 
> Xiong Zhang (1):
>       drm/i915/gvt: Correct the calculation of plane size
> 
> Yan Zhao (2):
>       drm/i915/gvt: do not deliver a workload if its creation fails
>       drm/i915/gvt: do not let pin count of shadow mm go negative
> 
>  drivers/gpu/drm/i915/gvt/display.c   | 2 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.c    | 8 ++------
>  drivers/gpu/drm/i915/gvt/gtt.c       | 2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c | 5 +++--
>  4 files changed, 7 insertions(+), 10 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

  reply	other threads:[~2019-04-04  0:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  9:40 [PULL] gvt-fixes Zhenyu Wang
2019-04-04  0:12 ` Rodrigo Vivi [this message]
2019-04-04  0:32   ` Zhenyu Wang
2019-04-04  1:03     ` Rodrigo Vivi
2019-04-04  0:39   ` Zhenyu Wang
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31  9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05  3:21   ` Zhenyu Wang
2019-11-22  3:33 Zhenyu Wang
2019-11-12  6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-08-13  9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-07-23  9:29 Zhenyu Wang
2019-07-29  3:33 ` Zhenyu Wang
2019-07-29 11:05   ` Jani Nikula
2019-07-30  7:00     ` Zhenyu Wang
2019-07-30  8:33       ` Jani Nikula
2019-06-19  6:22 Zhenyu Wang
2019-06-19  7:56 ` Jani Nikula
2019-06-05  8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-05-29  9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30  3:41   ` Zhenyu Wang
2019-05-31  8:16     ` Joonas Lahtinen
2019-05-21  6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11  6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-03-21  3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24  5:48 Zhenyu Wang
2019-01-31  9:45 ` 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=20190404001237.GA18158@intel.com \
    --to=rodrigo.vivi@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=zhenyuw@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.