From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/guc: Fix request re-submission after reset
Date: Fri, 10 Mar 2017 07:53:16 +0000 [thread overview]
Message-ID: <a730fce7-60e6-b977-d9ec-fb4ffcf4be73@linux.intel.com> (raw)
In-Reply-To: <20170309205540.GC28427@nuc-i3427.alporthouse.com>
On 09/03/2017 20:55, Chris Wilson wrote:
> On Thu, Mar 09, 2017 at 04:47:52PM -0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: series starting with [CI,1/2] drm/i915/guc: Fix request re-submission after reset
>> URL : https://patchwork.freedesktop.org/series/20991/
>> State : success
>>
>> == Summary ==
>>
>> Series 20991v1 Series without cover letter
>> https://patchwork.freedesktop.org/api/1.0/series/20991/revisions/1/mbox/
>>
>> Test gem_exec_flush:
>> Subgroup basic-batch-kernel-default-uc:
>> incomplete -> PASS (fi-skl-6700k) fdo#100130
>
> Wait... Did that just fix the bxt fails! My hero! :)
It was the team effort I think since you found it while testing the
scheduler support.
Pushed now, thanks for the review!
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-03-10 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 13:20 [CI 1/2] drm/i915/guc: Fix request re-submission after reset Tvrtko Ursulin
2017-03-09 13:20 ` [CI 2/2] HAX enable guc submission for CI Tvrtko Ursulin
2017-03-09 16:47 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/guc: Fix request re-submission after reset Patchwork
2017-03-09 20:55 ` Chris Wilson
2017-03-10 7:53 ` Tvrtko Ursulin [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=a730fce7-60e6-b977-d9ec-fb4ffcf4be73@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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