public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	igvt-g-dev <igvt-g-dev@lists.01.org>
Subject: Re: [PULL] GVT-g device model fix
Date: Fri, 02 Dec 2016 16:33:41 +0200	[thread overview]
Message-ID: <877f7iz9h6.fsf@intel.com> (raw)
In-Reply-To: <20161130193113.uxwuhcqctrj2cei2@phenom.ffwll.local>

On Wed, 30 Nov 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Nov 30, 2016 at 04:23:02PM +0800, Zhenyu Wang wrote:
>> 
>> Hi,
>> 
>> Here's current left GVT-g device model bug fixes for pull.
>
> Since 4.10 feature freeze is already done, this needs to go into
> drm-intel-next-fixes. Jani, can you pls pull?

Pulled,
Jani.

>
> Thanks, Daniel
>
>> 
>> Thanks.
>> 
>> ---
>> 
>> The following changes since commit 53e86ada8e53fcdbe1593f70b7df85549ba70b9a:
>> 
>>   drm/i915/gvt: remove unresolved vfio pin/unpin pages interface dependency (2016-11-17 15:51:16 +0800)
>> 
>> are available in the git repository at:
>> 
>>   https://github.com/01org/gvt-linux tags/gvt-next-2016-11-30
>> 
>> for you to fetch changes up to 53d6f812c0dbf1c9cad89b1c2118e61c13ca9677:
>> 
>>   drm/i915/gvt: fix lock not released bug for dispatch_workload() err path (2016-11-25 09:18:11 +0800)
>> 
>> ----------------------------------------------------------------
>> gvt-next-2016-11-30
>> 
>> - initialize vgpu as primary for correct cfg space setting
>> - fix 64 bit bar emulation
>> - fix un-released lock issue on dispatch workload err path
>> 
>> ----------------------------------------------------------------
>> Du, Changbin (1):
>>       drm/i915/gvt: fix missing init param.primary
>> 
>> Xiaoguang Chen (1):
>>       drm/i915/gvt: fix getting 64bit bar size error
>> 
>> Zhenyu Wang (1):
>>       drm/i915/gvt: fix lock not released bug for dispatch_workload() err path
>> 
>>  drivers/gpu/drm/i915/gvt/gvt.h       |  2 ++
>>  drivers/gpu/drm/i915/gvt/scheduler.c | 10 ++++++----
>>  drivers/gpu/drm/i915/gvt/vgpu.c      |  1 +
>>  3 files changed, 9 insertions(+), 4 deletions(-)
>> 
>> -- 
>> Open Source Technology Center, Intel ltd.
>> 
>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

-- 
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:[~2016-12-02 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30  8:23 [PULL] GVT-g device model fix Zhenyu Wang
2016-11-30 19:31 ` Daniel Vetter
2016-12-02 14:33   ` 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=877f7iz9h6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=igvt-g-dev@lists.01.org \
    --cc=intel-gfx@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