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>,
igvt-g-dev <igvt-g-dev@lists.01.org>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [GIT PULL] GVT-g fixes for 4.10
Date: Tue, 27 Dec 2016 13:04:04 +0200 [thread overview]
Message-ID: <87mvfh4orf.fsf@intel.com> (raw)
In-Reply-To: <20161226085503.5pabq2cfuexz77hc@zhen-hp.sh.intel.com>
On Mon, 26 Dec 2016, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> This is current GVT-g device model fixes for 4.10. I need to
> base on v4.10-rc1 for merged vfio and KVMGT support.
Pulled to drm-intel-fixes, thanks.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-27 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 8:55 [GIT PULL] GVT-g fixes for 4.10 Zhenyu Wang
2016-12-27 11:04 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-22 8:29 [git pull] " Zhenyu Wang
2016-12-22 9:35 ` 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=87mvfh4orf.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel@ffwll.ch \
--cc=igvt-g-dev@lists.01.org \
--cc=intel-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox