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>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-next for 4.20
Date: Fri, 7 Sep 2018 10:47:10 +0800 [thread overview]
Message-ID: <20180907024710.GO20737@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <153623948080.1020.13394850026154451501@ssahai-mobl2.gar.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
On 2018.09.06 16:11:20 +0300, Joonas Lahtinen wrote:
> Quoting Zhenyu Wang (2018-09-04 06:01:54)
> >
> > Hi,
> >
> > Here's initial gvt-next for 4.20 with two optimization for
> > guest context shadowing and command parser, and with W=1 build fixes.
>
> Thanks, pulled this, but it had one merge conflict (in gvt/reg.h).
> Please make sure the resolution I put in into drm-intel-next is correct.
>
yeah, forgot to mention conflict with recent PCH reg define
change. Merge change is correct.
Thanks!
--
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
prev parent reply other threads:[~2018-09-07 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 3:01 [PULL] gvt-next for 4.20 Zhenyu Wang
2018-09-06 13:11 ` Joonas Lahtinen
2018-09-07 2:47 ` Zhenyu Wang [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=20180907024710.GO20737@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=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