From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/pmu: Do not assume fixed hrtimer period
Date: Mon, 04 Jun 2018 13:26:25 -0000 [thread overview]
Message-ID: <20180604132625.6499.55089@emeril.freedesktop.org> (raw)
In-Reply-To: <20180604125239.5856-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915/pmu: Do not assume fixed hrtimer period
URL : https://patchwork.freedesktop.org/series/44191/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4275 -> Patchwork_9184 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/44191/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_9184 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_suspend@basic-s3:
fi-skl-gvtdvm: NOTRUN -> INCOMPLETE (fdo#105600, fdo#104108)
==== Possible fixes ====
igt@debugfs_test@read_all_entries:
fi-bdw-gvtdvm: DMESG-WARN (fdo#105600) -> PASS +2
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-cnl-psr: DMESG-WARN (fdo#104951) -> PASS
fdo#104108 https://bugs.freedesktop.org/show_bug.cgi?id=104108
fdo#104951 https://bugs.freedesktop.org/show_bug.cgi?id=104951
fdo#105600 https://bugs.freedesktop.org/show_bug.cgi?id=105600
== Participating hosts (40 -> 39) ==
Additional (3): fi-hsw-peppy fi-skl-guc fi-skl-gvtdvm
Missing (4): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-skl-6700hq
== Build changes ==
* Linux: CI_DRM_4275 -> Patchwork_9184
CI_DRM_4275: 8fdb62e0511e81fa935059c274a2457361fdb679 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4505: 8a8f0271a71e2e0d2a2caa4d41f4ad1d9c89670e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9184: 9461f26f5ca17e53d311f5c2a1e823e99586c8fd @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9461f26f5ca1 drm/i915/pmu: Do not assume fixed hrtimer period
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9184/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-04 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 12:52 [PATCH] drm/i915/pmu: Do not assume fixed hrtimer period Tvrtko Ursulin
2018-06-04 12:59 ` Chris Wilson
2018-06-04 13:03 ` Chris Wilson
2018-06-04 15:01 ` Tvrtko Ursulin
2018-06-04 15:11 ` Chris Wilson
2018-06-05 8:51 ` Tvrtko Ursulin
2018-06-05 9:06 ` Chris Wilson
2018-06-05 11:35 ` Tvrtko Ursulin
2018-06-05 11:42 ` Chris Wilson
2018-06-04 13:05 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-06-04 13:26 ` Patchwork [this message]
2018-06-04 14:17 ` ✓ Fi.CI.IGT: success " Patchwork
2018-06-05 10:57 ` ✗ Fi.CI.BAT: failure for drm/i915/pmu: Do not assume fixed hrtimer period (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=20180604132625.6499.55089@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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.