From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Use new i915_gem_object_pin_map for LRC
Date: Tue, 12 Apr 2016 10:35:17 +0100 [thread overview]
Message-ID: <20160412093517.GK20240@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20160412092453.10586.89297@emeril.freedesktop.org>
On Tue, Apr 12, 2016 at 09:24:53AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Use new i915_gem_object_pin_map for LRC
> URL : https://patchwork.freedesktop.org/series/5580/
> State : failure
>
> == Summary ==
>
> Series 5580v1 drm/i915: Use new i915_gem_object_pin_map for LRC
> http://patchwork.freedesktop.org/api/1.0/series/5580/revisions/1/mbox/
>
> Test drv_module_reload_basic:
> pass -> DMESG-WARN (bsw-nuc-2)
> pass -> DMESG-WARN (skl-nuci5)
> pass -> DMESG-WARN (bdw-nuci7)
> pass -> DMESG-WARN (skl-i7k-2)
> pass -> DMESG-WARN (bdw-ultra)
Hmm, I guess we have a leak?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-12 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 8:52 [PATCH] drm/i915: Use new i915_gem_object_pin_map for LRC Tvrtko Ursulin
2016-04-12 9:24 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-12 9:35 ` Chris Wilson [this message]
2016-04-12 9:30 ` [PATCH] " Chris Wilson
2016-04-12 9:36 ` Tvrtko Ursulin
2016-04-12 9:42 ` Chris Wilson
2016-04-12 9:43 ` Chris Wilson
2016-04-12 10:33 ` Tvrtko Ursulin
2016-04-12 13:05 ` [PATCH v3] " Tvrtko Ursulin
2016-04-12 13:12 ` Chris Wilson
2016-04-12 13:19 ` Tvrtko Ursulin
2016-04-12 13:29 ` Chris Wilson
2016-04-12 14:06 ` ✗ Fi.CI.BAT: failure for drm/i915: Use new i915_gem_object_pin_map for LRC (rev2) Patchwork
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=20160412093517.GK20240@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.