From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Mika Kuoppala" <mika.kuoppala@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ Xe.CI.FULL: success for drm/xe: Remove ifdef in DRM_GPUVA_OP_DRIVER svm subop checking
Date: Wed, 15 Jul 2026 12:52:58 -0000 [thread overview]
Message-ID: <178411997808.190770.13927459474641555026@6beec6c84f66> (raw)
In-Reply-To: <20260715103104.63954-1-mika.kuoppala@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
== Series Details ==
Series: drm/xe: Remove ifdef in DRM_GPUVA_OP_DRIVER svm subop checking
URL : https://patchwork.freedesktop.org/series/170474/
State : success
== Summary ==
CI Bug Log - changes from xe-5409-6dd678fdc2f39062bed466d7e3c851736e376531_FULL -> xe-pw-170474v1_FULL
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (2 -> 2)
------------------------------
No changes in participating hosts
Changes
-------
No changes found
Build changes
-------------
* Linux: xe-5409-6dd678fdc2f39062bed466d7e3c851736e376531 -> xe-pw-170474v1
IGT_9006: 6380a8af26359dd222e22679442272ded836c463 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-5409-6dd678fdc2f39062bed466d7e3c851736e376531: 6dd678fdc2f39062bed466d7e3c851736e376531
xe-pw-170474v1: 170474v1
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-170474v1/index.html
[-- Attachment #2: Type: text/html, Size: 1524 bytes --]
prev parent reply other threads:[~2026-07-15 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 10:31 [PATCH] drm/xe: Remove ifdef in DRM_GPUVA_OP_DRIVER svm subop checking Mika Kuoppala
2026-07-15 11:06 ` ✓ CI.KUnit: success for " Patchwork
2026-07-15 11:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-15 12:28 ` [PATCH] " Matthew Auld
2026-07-15 20:00 ` Matthew Brost
2026-07-15 12:52 ` Patchwork [this message]
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=178411997808.190770.13927459474641555026@6beec6c84f66 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kuoppala@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