All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@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: [Intel-gfx] [PULL] gvt-next-fixes
Date: Thu, 5 Dec 2019 14:11:41 +0800	[thread overview]
Message-ID: <20191205061141.GF4196@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20191202051711.GZ4196@zhen-hp.sh.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1791 bytes --]


ping..

On 2019.12.02 13:17:11 +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> More gvt fixes for 5.5-rc. One is MI_ATOMIC cmd parser fix which
> missed 5.4 and another two for CFL non-priv reg access fixes.
> 
> Thanks
> --
> The following changes since commit 83faaf074e6d1ca4d1441aded0d3f01bce413479:
> 
>   drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08 11:08:07 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2019-12-02
> 
> for you to fetch changes up to 92b1aa773fadb4e2a90ed5d3beecb422d568ad9a:
> 
>   drm/i915/gvt: Fix cmd length check for MI_ATOMIC (2019-12-02 11:06:49 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2019-12-02
> 
> - Fix cmd parser for MI_ATOMIC (Zhenyu)
> - Fix non-priv register access warning on CFL (Fred)
> 
> ----------------------------------------------------------------
> Gao, Fred (2):
>       drm/i915/gvt: Refine non privilege register address calucation
>       drm/i915/gvt: Update force-to-nonpriv register whitelist
> 
> Zhenyu Wang (1):
>       drm/i915/gvt: Fix cmd length check for MI_ATOMIC
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
>  drivers/gpu/drm/i915/gvt/handlers.c   | 5 +++--
>  2 files changed, 6 insertions(+), 5 deletions(-)
> 
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev


-- 
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: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-05  6:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  5:17 [PULL] gvt-next-fixes Zhenyu Wang
2019-12-02  5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05  6:11 ` Zhenyu Wang [this message]
2019-12-05  8:14   ` Joonas Lahtinen
2019-12-05  8:49     ` Zhenyu Wang
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28  7:47 Zhenyu Wang
2023-02-23  8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21  9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31  7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula
2020-04-07 23:36             ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` Zhenyu Wang
2019-11-20 11:25   ` Joonas Lahtinen
2019-11-20 11:25     ` Joonas Lahtinen

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=20191205061141.GF4196@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=joonas.lahtinen@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.