public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: warning for drm/i915: Fix nesting of filelist_mutex vs struct_mutex in i915_ppgtt_info
Date: Mon, 22 Aug 2016 12:11:45 -0000	[thread overview]
Message-ID: <20160822121145.3032.7524@emeril.freedesktop.org> (raw)
In-Reply-To: <20160822113526.23553-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Fix nesting of filelist_mutex vs struct_mutex in i915_ppgtt_info
URL   : https://patchwork.freedesktop.org/series/11411/
State : warning

== Summary ==

Series 11411v1 drm/i915: Fix nesting of filelist_mutex vs struct_mutex in i915_ppgtt_info
http://patchwork.freedesktop.org/api/1.0/series/11411/revisions/1/mbox

Test gem_exec_suspend:
        Subgroup basic-s3:
                dmesg-warn -> PASS       (ro-bdw-i7-5557U)
Test kms_flip:
        Subgroup basic-plain-flip:
                dmesg-warn -> PASS       (ro-bdw-i7-5557U)
Test kms_pipe_crc_basic:
        Subgroup suspend-read-crc-pipe-b:
                dmesg-warn -> SKIP       (ro-bdw-i7-5557U)
                skip       -> DMESG-WARN (ro-bdw-i5-5250u)
        Subgroup suspend-read-crc-pipe-c:
                skip       -> DMESG-WARN (ro-bdw-i5-5250u)

fi-hsw-i7-4770k  total:107  pass:91   dwarn:0   dfail:0   fail:0   skip:15 
fi-kbl-qkkr      total:244  pass:186  dwarn:29  dfail:0   fail:2   skip:27 
fi-skl-i7-6700k  total:244  pass:210  dwarn:4   dfail:2   fail:0   skip:28 
fi-snb-i7-2600   total:244  pass:198  dwarn:4   dfail:0   fail:0   skip:42 
ro-bdw-i5-5250u  total:240  pass:219  dwarn:5   dfail:0   fail:0   skip:16 
ro-bdw-i7-5557U  total:240  pass:220  dwarn:1   dfail:0   fail:0   skip:19 
ro-bdw-i7-5600u  total:240  pass:206  dwarn:0   dfail:0   fail:2   skip:32 
ro-bsw-n3050     total:240  pass:194  dwarn:0   dfail:0   fail:4   skip:42 
ro-byt-n2820     total:240  pass:196  dwarn:0   dfail:0   fail:4   skip:40 
ro-hsw-i3-4010u  total:240  pass:213  dwarn:0   dfail:0   fail:1   skip:26 
ro-hsw-i7-4770r  total:240  pass:185  dwarn:0   dfail:0   fail:0   skip:55 
ro-ilk1-i5-650   total:235  pass:174  dwarn:0   dfail:0   fail:2   skip:59 
ro-ivb-i7-3770   total:240  pass:204  dwarn:0   dfail:0   fail:1   skip:35 
ro-ivb2-i7-3770  total:240  pass:208  dwarn:0   dfail:0   fail:1   skip:31 
ro-skl3-i5-6260u total:240  pass:225  dwarn:0   dfail:0   fail:1   skip:14 

Results at /archive/results/CI_IGT_test/RO_Patchwork_1963/

020f7af drm-intel-nightly: 2016y-08m-22d-11h-29m-35s UTC integration manifest
8ab3127 drm/i915: Fix nesting of filelist_mutex vs struct_mutex in i915_ppgtt_info

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-08-22 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 11:35 [PATCH] drm/i915: Fix nesting of filelist_mutex vs struct_mutex in i915_ppgtt_info Chris Wilson
2016-08-22 11:44 ` Joonas Lahtinen
2016-08-22 12:09 ` Jani Nikula
2016-08-22 12:15   ` Chris Wilson
2016-08-22 12:28     ` Jani Nikula
2016-08-22 12:11 ` 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=20160822121145.3032.7524@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox