From: Patchwork <patchwork@emeril.freedesktop.org>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for series starting with [1/2] drm/syncobj: Mark up the fence as an RCU protected pointer
Date: Fri, 01 Sep 2017 18:55:14 -0000 [thread overview]
Message-ID: <20170901185514.7605.57190@emeril.freedesktop.org> (raw)
In-Reply-To: <20170901145707.21309-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/syncobj: Mark up the fence as an RCU protected pointer
URL : https://patchwork.freedesktop.org/series/29700/
State : success
== Summary ==
Test perf:
Subgroup polling:
fail -> PASS (shard-hsw) fdo#102252
fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
shard-hsw total:2263 pass:1233 dwarn:0 dfail:0 fail:14 skip:1015 time:9439s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_5565/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-09-01 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:57 [PATCH 1/2] drm/syncobj: Mark up the fence as an RCU protected pointer Chris Wilson
2017-09-01 14:57 ` [PATCH 2/2] dma-buf/fence: Sparse wants __rcu on the object itself Chris Wilson
2017-09-01 15:30 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/syncobj: Mark up the fence as an RCU protected pointer Patchwork
2017-09-01 16:27 ` [PATCH 1/2] " Ville Syrjälä
2017-09-01 18:55 ` Patchwork [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=20170901185514.7605.57190@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 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.