From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Kunal Joshi <kunal1.joshi@intel.com>,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: [PATCH i-g-t] tests/intel/kms_dp_link_training: Add missing DRIVER_XE
Date: Thu, 6 Mar 2025 16:25:52 +0100 [thread overview]
Message-ID: <20250306152552.1620737-1-marcin.bernatowicz@linux.intel.com> (raw)
Commit d7bccece44dd ("tests/intel/kms_dp_link_training: Restrict to Intel
GPUs") missed adding DRIVER_XE. Ensure both DRIVER_INTEL and DRIVER_XE
are set to properly restrict the test to Intel GPUs.
Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Cc: Arun R Murthy <arun.r.murthy@intel.com>
---
tests/intel/kms_dp_link_training.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/intel/kms_dp_link_training.c b/tests/intel/kms_dp_link_training.c
index 7d3848b94..3df7b6562 100644
--- a/tests/intel/kms_dp_link_training.c
+++ b/tests/intel/kms_dp_link_training.c
@@ -335,7 +335,7 @@ igt_main
data_t data = {};
igt_fixture {
- data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
+ data.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_XE);
data.devid = intel_get_drm_devid(data.drm_fd);
kmstest_set_vt_graphics_mode();
igt_display_require(&data.display, data.drm_fd);
--
2.31.1
next reply other threads:[~2025-03-06 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 15:25 Marcin Bernatowicz [this message]
2025-03-06 17:18 ` [PATCH i-g-t] tests/intel/kms_dp_link_training: Add missing DRIVER_XE Kamil Konieczny
2025-03-06 19:01 ` Kamil Konieczny
2025-03-07 2:38 ` ✗ Fi.CI.BAT: failure 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=20250306152552.1620737-1-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=kunal1.joshi@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