From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, Dave Gordon <david.s.gordon@intel.com>
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: fix potential dangling else problems in for_each_ macros (rev4)
Date: Thu, 24 Mar 2016 14:35:48 +0000 [thread overview]
Message-ID: <56F3FB44.8010201@linux.intel.com> (raw)
In-Reply-To: <20160324120325.1550.34779@emeril.freedesktop.org>
On 24/03/16 12:03, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: fix potential dangling else problems in for_each_ macros (rev4)
> URL : https://patchwork.freedesktop.org/series/1142/
> State : success
>
> == Summary ==
>
> Series 1142v4 drm/i915: fix potential dangling else problems in for_each_ macros
> http://patchwork.freedesktop.org/api/1.0/series/1142/revisions/4/mbox/
>
> Test gem_exec_suspend:
> Subgroup basic-s3:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-a:
> pass -> SKIP (byt-nuc)
> Subgroup suspend-read-crc-pipe-c:
> incomplete -> PASS (hsw-gt2)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> dmesg-warn -> PASS (byt-nuc)
>
> bdw-nuci7 total:192 pass:180 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:192 pass:171 dwarn:0 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:192 pass:155 dwarn:0 dfail:0 fail:0 skip:37
> byt-nuc total:192 pass:156 dwarn:0 dfail:0 fail:0 skip:36
> hsw-brixbox total:192 pass:170 dwarn:0 dfail:0 fail:0 skip:22
> hsw-gt2 total:192 pass:175 dwarn:0 dfail:0 fail:0 skip:17
> ivb-t430s total:192 pass:167 dwarn:0 dfail:0 fail:0 skip:25
> skl-i7k-2 total:192 pass:169 dwarn:0 dfail:0 fail:0 skip:23
> skl-nuci5 total:192 pass:181 dwarn:0 dfail:0 fail:0 skip:11
> snb-dellxps total:192 pass:158 dwarn:0 dfail:0 fail:0 skip:34
> snb-x220t total:192 pass:158 dwarn:0 dfail:0 fail:1 skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1704/
>
> 79ee42317266a82b932a39e9567244ed91dd27d6 drm-intel-nightly: 2016y-03m-24d-10h-26m-54s UTC integration manifest
> 0126b0b851d5abdfc08ccd48cf2babf2fdd550c0 drm/i915: replace for_each_engine()
> 6fe2515ba81fbeaf484a388941b776350f910ba2 drm/i915: introduce for_each_engine_id()
Merged, thanks for patches and 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:[~2016-03-24 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 17:36 [RFC PATCH] drm/i915: fix potential dangling else problems in for_each_ macros Jani Nikula
2015-11-24 17:38 ` Jani Nikula
2015-11-24 18:25 ` Daniel Vetter
2015-11-24 22:26 ` Chris Wilson
2015-11-24 23:47 ` Chris Wilson
2015-11-25 9:10 ` Jani Nikula
2015-11-25 9:23 ` Daniel Vetter
2015-12-02 13:29 ` Dave Gordon
2015-12-02 13:46 ` Chris Wilson
2015-12-02 14:51 ` Dave Gordon
2015-12-02 14:58 ` Chris Wilson
2015-12-02 18:18 ` Dave Gordon
2015-12-10 12:32 ` [RFC] drm/i915: for_each_engine() Dave Gordon
2015-12-10 12:42 ` Chris Wilson
2016-03-23 18:19 ` [PATCH 0/2] Updating and simplifying for_each_engine() Dave Gordon
2016-03-23 18:19 ` [PATCH 1/2] drm/i915: introduce for_each_engine_id() Dave Gordon
2016-03-23 18:19 ` [PATCH 2/2] drm/i915: replace for_each_engine() Dave Gordon
2016-03-23 20:43 ` Chris Wilson
2016-03-24 11:20 ` [PATCH 2/2 v2] " Dave Gordon
2016-03-24 9:06 ` ✗ Fi.CI.BAT: failure for drm/i915: fix potential dangling else problems in for_each_ macros (rev3) Patchwork
2016-03-24 11:38 ` Dave Gordon
2016-03-24 12:03 ` ✓ Fi.CI.BAT: success for drm/i915: fix potential dangling else problems in for_each_ macros (rev4) Patchwork
2016-03-24 14:35 ` 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=56F3FB44.8010201@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=david.s.gordon@intel.com \
--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.