From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for intel_engine_cs renaming bomb (rev3)
Date: Fri, 11 Mar 2016 09:49:29 +0000 [thread overview]
Message-ID: <56E294A9.5090508@linux.intel.com> (raw)
In-Reply-To: <20160310163037.30213.40490@emeril.freedesktop.org>
On 10/03/16 16:30, Patchwork wrote:
> == Series Details ==
>
> Series: intel_engine_cs renaming bomb (rev3)
> URL : https://patchwork.freedesktop.org/series/4303/
> State : warning
>
> == Summary ==
>
> Series 4303v3 intel_engine_cs renaming bomb
> http://patchwork.freedesktop.org/api/1.0/series/4303/revisions/3/mbox/
>
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=93787
> Subgroup basic-flip-vs-modeset:
> dmesg-warn -> PASS (bdw-ultra)
> Subgroup basic-plain-flip:
> pass -> DMESG-WARN (hsw-brixbox)
Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94349
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-b:
> incomplete -> PASS (hsw-gt2)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> fail -> DMESG-FAIL (snb-x220t)
Again unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94349
> dmesg-warn -> PASS (snb-dellxps)
> dmesg-warn -> PASS (hsw-brixbox)
> Subgroup basic-rte:
> dmesg-warn -> PASS (snb-x220t)
> dmesg-warn -> PASS (bsw-nuc-2)
>
> bdw-nuci7 total:193 pass:181 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:193 pass:172 dwarn:0 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:193 pass:156 dwarn:0 dfail:0 fail:0 skip:37
> byt-nuc total:193 pass:158 dwarn:0 dfail:0 fail:0 skip:35
> hsw-brixbox total:193 pass:170 dwarn:1 dfail:0 fail:0 skip:22
> hsw-gt2 total:193 pass:176 dwarn:0 dfail:0 fail:0 skip:17
> ilk-hp8440p total:193 pass:129 dwarn:1 dfail:0 fail:0 skip:63
> ivb-t430s total:193 pass:168 dwarn:0 dfail:0 fail:0 skip:25
> skl-i5k-2 total:193 pass:170 dwarn:0 dfail:0 fail:0 skip:23
> skl-i7k-2 total:193 pass:170 dwarn:0 dfail:0 fail:0 skip:23
> skl-nuci5 total:161 pass:152 dwarn:0 dfail:0 fail:0 skip:9
> snb-dellxps total:193 pass:158 dwarn:1 dfail:0 fail:0 skip:34
> snb-x220t total:193 pass:159 dwarn:0 dfail:1 fail:0 skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1565/
>
> 63461ba49f1bc63fe9dcccdbbaa3a5049c57ae37 drm-intel-nightly: 2016y-03m-10d-13h-21m-51s UTC integration manifest
> 434af94ce2882d30b6a179231e7e15de9c32f78c drm/i915: More renaming of rings to engines
> e21ab7713d974e6d1001ea13fab23c80aaa46500 drm/i915: More intel_engine_cs renaming
> f9c4ea7fc64c8a4a28c8315f908711e959261d95 drm/i915: Rename intel_engine_cs struct members
> c038a428c10d8f6976cd42b94371d8b97890945a drm/i915: Rename intel_engine_cs function parameters
> 310c63e721cbc868fc15d831da6abb09be5de102 drm/i915: Rename local struct intel_engine_cs variables
So looking good to merge.
Any objections wrt rebasing pain? John maybe? :) How exposed your patch
series are to code which deals a lot with intel_engine_cs?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-11 9:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 14:21 [PATCH 0/5] intel_engine_cs renaming bomb Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 1/5] drm/i915: Rename local struct intel_engine_cs variables Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 2/5] drm/i915: Rename intel_engine_cs function parameters Tvrtko Ursulin
2016-03-10 15:33 ` kbuild test robot
2016-03-10 14:21 ` [PATCH 3/5] drm/i915: Rename intel_engine_cs struct members Tvrtko Ursulin
2016-03-10 15:18 ` kbuild test robot
2016-03-10 15:47 ` [PATCH 3/5 v2] " Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 4/5] drm/i915: More intel_engine_cs renaming Tvrtko Ursulin
2016-03-10 15:47 ` [PATCH 4/5 v2] " Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 5/5] drm/i915: More renaming of rings to engines Tvrtko Ursulin
2016-03-10 14:49 ` Chris Wilson
2016-03-10 14:59 ` Tvrtko Ursulin
2016-03-11 11:38 ` [PATCH v2 " Tvrtko Ursulin
2016-03-11 13:19 ` [PATCH 5/5 v3] " Tvrtko Ursulin
2016-03-10 14:52 ` [PATCH 0/5] intel_engine_cs renaming bomb Chris Wilson
2016-03-10 15:00 ` Arun Siluvery
2016-03-10 16:28 ` Tvrtko Ursulin
2016-03-10 16:43 ` Arun Siluvery
2016-03-10 16:47 ` Tvrtko Ursulin
2016-03-10 15:10 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-03-10 16:30 ` ✗ Fi.CI.BAT: warning for intel_engine_cs renaming bomb (rev3) Patchwork
2016-03-11 9:49 ` Tvrtko Ursulin [this message]
2016-03-11 9:52 ` Arun Siluvery
2016-03-11 12:30 ` ✗ Fi.CI.BAT: warning for intel_engine_cs renaming bomb (rev4) Patchwork
2016-03-11 14:32 ` ✗ Fi.CI.BAT: failure for intel_engine_cs renaming bomb (rev5) 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=56E294A9.5090508@linux.intel.com \
--to=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox