From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chaitanya Kumar Borah" <chaitanya.kumar.borah@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ Xe.CI.BAT: success for drm/colorop: Keep colorop state consistent across atomic commits (rev2)
Date: Wed, 18 Feb 2026 12:23:10 -0000 [thread overview]
Message-ID: <177141739089.261925.6239324256214715959@a3b018990fe9> (raw)
In-Reply-To: <20260218065713.326417-1-chaitanya.kumar.borah@intel.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
== Series Details ==
Series: drm/colorop: Keep colorop state consistent across atomic commits (rev2)
URL : https://patchwork.freedesktop.org/series/161742/
State : success
== Summary ==
CI Bug Log - changes from xe-4572-fc9512d31fa2c190f58c85dbdf7313d2d0ad4b0d_BAT -> xe-pw-161742v2_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (14 -> 14)
------------------------------
No changes in participating hosts
Changes
-------
No changes found
Build changes
-------------
* Linux: xe-4572-fc9512d31fa2c190f58c85dbdf7313d2d0ad4b0d -> xe-pw-161742v2
IGT_8758: 8758
xe-4572-fc9512d31fa2c190f58c85dbdf7313d2d0ad4b0d: fc9512d31fa2c190f58c85dbdf7313d2d0ad4b0d
xe-pw-161742v2: 161742v2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161742v2/index.html
[-- Attachment #2: Type: text/html, Size: 1442 bytes --]
next prev parent reply other threads:[~2026-02-18 12:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 6:57 [PATCH 0/2] drm/colorop: Keep colorop state consistent across atomic commits Chaitanya Kumar Borah
2026-02-18 6:57 ` [PATCH 1/2] drm/colorop: Preserve bypass value in duplicate_state() Chaitanya Kumar Borah
2026-02-23 20:33 ` Shankar, Uma
2026-02-18 6:57 ` [PATCH 2/2] drm/atomic: Add affected colorops with affected planes Chaitanya Kumar Borah
2026-02-23 20:37 ` Shankar, Uma
2026-03-10 21:07 ` Borah, Chaitanya Kumar
2026-02-18 7:42 ` ✓ CI.KUnit: success for drm/colorop: Keep colorop state consistent across atomic commits Patchwork
2026-02-18 8:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 8:32 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-18 10:52 ` ✓ CI.KUnit: success for drm/colorop: Keep colorop state consistent across atomic commits (rev2) Patchwork
2026-02-18 12:23 ` Patchwork [this message]
2026-02-18 13:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-23 21:14 ` [PATCH 0/2] drm/colorop: Keep colorop state consistent across atomic commits Harry Wentland
2026-02-24 8:59 ` Shankar, Uma
2026-02-26 5:59 ` Borah, Chaitanya Kumar
2026-03-10 21:00 ` Borah, Chaitanya Kumar
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=177141739089.261925.6239324256214715959@a3b018990fe9 \
--to=patchwork@emeril.freedesktop.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-xe@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