Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Force a LUT update in intel_initial_commit()
Date: Tue, 20 Nov 2018 14:29:18 -0000	[thread overview]
Message-ID: <20181120142918.22659.9023@emeril.freedesktop.org> (raw)
In-Reply-To: <20181120135450.3634-1-ville.syrjala@linux.intel.com>

== Series Details ==

Series: series starting with [1/2] drm/i915: Force a LUT update in intel_initial_commit()
URL   : https://patchwork.freedesktop.org/series/52754/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_5172 -> Patchwork_10861 =

== Summary - SUCCESS ==

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/52754/revisions/1/mbox/

== Possible new issues ==

  Here are the unknown changes that may have been introduced in Patchwork_10861:

  === IGT changes ===

    ==== Possible regressions ====

    {igt@runner@aborted}:
      {fi-icl-y}:         NOTRUN -> FAIL

    
== Known issues ==

  Here are the changes found in Patchwork_10861 that come from known issues:

  === IGT changes ===

    ==== Issues hit ====

    igt@gem_ctx_create@basic-files:
      fi-icl-u2:          PASS -> DMESG-WARN (fdo#107724)

    igt@gem_exec_suspend@basic-s4-devices:
      fi-blb-e6850:       PASS -> INCOMPLETE (fdo#107718)

    
    ==== Possible fixes ====

    igt@gem_ctx_switch@basic-default:
      fi-icl-u2:          DMESG-WARN (fdo#107724) -> PASS

    igt@kms_frontbuffer_tracking@basic:
      fi-hsw-peppy:       DMESG-WARN (fdo#102614) -> PASS

    igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
      fi-kbl-7560u:       FAIL (fdo#103375) -> PASS

    
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
  fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
  fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
  fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724


== Participating hosts (51 -> 46) ==

  Additional (1): fi-icl-y 
  Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-u3 


== Build changes ==

    * Linux: CI_DRM_5172 -> Patchwork_10861

  CI_DRM_5172: 469c356dc6c310bed869703bfc75a56cd63075b5 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4721: 68264891ceee34195839d82d4d87cbae08ef2431 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10861: e9005dd0153e45c85de821d4fc30ea89ec4e1e04 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

e9005dd0153e drm/i915: Add rotation readout for plane initial config
22d340f39fee drm/i915: Force a LUT update in intel_initial_commit()

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10861/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-11-20 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 13:54 [PATCH 1/2] drm/i915: Force a LUT update in intel_initial_commit() Ville Syrjala
2018-11-20 13:54 ` [PATCH 2/2] drm/i915: Add rotation readout for plane initial config Ville Syrjala
2018-11-20 22:20   ` Rodrigo Vivi
2018-11-21 11:34     ` Maarten Lankhorst
2018-11-21 12:13     ` Ville Syrjälä
2018-11-20 14:29 ` Patchwork [this message]
2018-11-20 18:34 ` [PATCH 1/2] drm/i915: Force a LUT update in intel_initial_commit() Hans de Goede
2018-11-20 20:54 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2018-11-20 22:25 ` [PATCH 1/2] " Rodrigo Vivi
2018-11-21 11:40   ` Ville Syrjälä

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=20181120142918.22659.9023@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /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