From: Matt Roper <matthew.d.roper@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✓ Xe.CI.BAT: success for drm/xe: Stop applying Wa_16018737384 from Xe3 onward
Date: Thu, 12 Feb 2026 16:22:34 -0800 [thread overview]
Message-ID: <20260213002234.GO4694@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <177086096023.247860.8275259072124891686@a3b018990fe9>
On Thu, Feb 12, 2026 at 01:49:20AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe: Stop applying Wa_16018737384 from Xe3 onward
> URL : https://patchwork.freedesktop.org/series/161518/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from xe-4545-b4bfe7d753afaf6ea4950111a309a4e2ef5aef68_BAT -> xe-pw-161518v1_BAT
> ====================================================
>
> Summary
> -------
>
> **SUCCESS**
>
> No regressions found.
Shards CI (Xe.CI.FULL) seems to be dead right now. But the shards pool
only has BMG and LNL hardware in it, so they wouldn't have any coverage
of the Xe3 change here anyway. Only BAT covers Xe3, so going ahead and
applying based on the results here. Thanks DN for the review.
Matt
>
>
>
> Participating hosts (12 -> 11)
> ------------------------------
>
> Missing (1): bat-bmg-3
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-161518v1_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Possible fixes ####
>
> * igt@xe_waitfence@abstime:
> - bat-dg2-oem2: [TIMEOUT][1] ([Intel XE#6506]) -> [PASS][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4545-b4bfe7d753afaf6ea4950111a309a4e2ef5aef68/bat-dg2-oem2/igt@xe_waitfence@abstime.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161518v1/bat-dg2-oem2/igt@xe_waitfence@abstime.html
>
>
> [Intel XE#6506]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6506
>
>
> Build changes
> -------------
>
> * Linux: xe-4545-b4bfe7d753afaf6ea4950111a309a4e2ef5aef68 -> xe-pw-161518v1
>
> IGT_8751: af788251f1ef729d17c802aec2c4547b52059e58 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-4545-b4bfe7d753afaf6ea4950111a309a4e2ef5aef68: b4bfe7d753afaf6ea4950111a309a4e2ef5aef68
> xe-pw-161518v1: 161518v1
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161518v1/index.html
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2026-02-13 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 23:47 [PATCH] drm/xe: Stop applying Wa_16018737384 from Xe3 onward Matt Roper
2026-02-12 1:12 ` ✓ CI.KUnit: success for " Patchwork
2026-02-12 1:49 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-13 0:22 ` Matt Roper [this message]
2026-02-12 13:36 ` [PATCH] " Bhadane, Dnyaneshwar
2026-02-13 7:03 ` ✓ Xe.CI.FULL: success for " 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=20260213002234.GO4694@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@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