public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "Nikkanen, Kimmo" <kimmo.nikkanen@intel.com>,
	intel-gfx@lists.freedesktop.org, "Xu,
	Terrence" <terrence.xu@intel.com>,
	igvt-g-dev@lists.01.org, Daniel Vetter <daniel.vetter@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: i915 and GTV-g maintenance, workflows and CI
Date: Thu, 20 Oct 2016 13:55:35 +0300	[thread overview]
Message-ID: <87wph3qogo.fsf@intel.com> (raw)
In-Reply-To: <20161020094237.kxg4g3l36k2izrk7@zhen-hp.sh.intel.com>

On Thu, 20 Oct 2016, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2016.10.20 11:24:21 +0200, Daniel Vetter wrote:
>> On Thu, Oct 20, 2016 at 12:02:54PM +0300, Jani Nikula wrote:
>> > * GVT-g bug management. Do you have something set up already? Would be
>> >   great to be able to use https://bugs.freedesktop.org so we could
>> >   reassign between i915 and GVT-g.
>> 
>> +1.
>
> yeah, that's also in our plan, will create new category for GVT-g driver.
> Our QA team will handle that.

Please connect them with Martin Peres (CC'd) who'll be able to get this
done.

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

      parent reply	other threads:[~2016-10-20 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  9:02 i915 and GTV-g maintenance, workflows and CI Jani Nikula
2016-10-20  9:24 ` Daniel Vetter
2016-10-20  9:42   ` Zhenyu Wang
2016-10-20 10:01     ` Chris Wilson
2016-10-20 10:34       ` Zhenyu Wang
2016-10-20 10:55     ` 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=87wph3qogo.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=igvt-g-dev@lists.01.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kimmo.nikkanen@intel.com \
    --cc=terrence.xu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox