From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info
Date: Tue, 02 Oct 2018 10:54:57 -0000 [thread overview]
Message-ID: <20181002105457.22073.73604@emeril.freedesktop.org> (raw)
In-Reply-To: <20181002083639.6907-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info
URL : https://patchwork.freedesktop.org/series/50431/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4913 -> Patchwork_10320 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/50431/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_10320 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@amdgpu/amd_cs_nop@sync-fork-compute0:
fi-kbl-8809g: PASS -> DMESG-WARN (fdo#107762)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-bdw-samus: NOTRUN -> INCOMPLETE (fdo#107773)
==== Possible fixes ====
igt@gem_exec_suspend@basic-s3:
fi-bdw-samus: INCOMPLETE (fdo#107773) -> PASS
fi-blb-e6850: INCOMPLETE (fdo#107718) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
fdo#107762 https://bugs.freedesktop.org/show_bug.cgi?id=107762
fdo#107773 https://bugs.freedesktop.org/show_bug.cgi?id=107773
== Participating hosts (46 -> 43) ==
Missing (3): fi-bsw-cyan fi-byt-squawks fi-icl-u2
== Build changes ==
* Linux: CI_DRM_4913 -> Patchwork_10320
CI_DRM_4913: 8841faa15ae85eff15d285c64353d2b75d7b400f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4660: d0975646c50568e66e65b44b81d28232d059b94e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10320: 8729ba6ac2497288cdcbae17ef8e1105aa721245 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8729ba6ac249 drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10320/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-10-02 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 8:36 [PATCH] drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info Chris Wilson
2018-10-02 10:54 ` Patchwork [this message]
2018-10-02 11:02 ` Tvrtko Ursulin
2018-10-02 11:11 ` Chris Wilson
2018-10-02 15:46 ` Ville Syrjälä
2018-10-02 16:01 ` Chris Wilson
2018-10-02 11:32 ` [PATCH v2] drm/i915: Show actual alongside requested " Chris Wilson
2018-10-02 11:41 ` Tvrtko Ursulin
2018-10-02 11:47 ` Chris Wilson
2018-10-02 12:24 ` ✓ Fi.CI.BAT: success for drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info (rev2) Patchwork
2018-10-02 20:47 ` ✗ Fi.CI.IGT: failure " 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=20181002105457.22073.73604@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