From: Aditya Chauhan <aditya.chauhan@intel.com>
To: ramadevi.gandi@intel.com, himanshu.girotra@intel.com,
swati2.sharma@intel.com, kamil.konieczny@intel.com,
igt-dev@lists.freedesktop.org
Subject: [PATCH v3 i-g-t 2/2] intel-ci: Add NVL Display blocklist to meson.build
Date: Thu, 12 Mar 2026 15:52:01 +0530 [thread overview]
Message-ID: <20260312102201.53909-3-aditya.chauhan@intel.com> (raw)
In-Reply-To: <20260312102201.53909-1-aditya.chauhan@intel.com>
Add NVL display blocklist to meson.build which was earlier missing.
Fixes: 04db3b26c52b ("intel-ci: Add NVL display blocklist")
v2: Make commit message more descriptive(Swati Sharma)
v3: Use correct subject(intel-ci) and take care of
Alphabetical order while adding to meson.build(Swati Sharma)
Signed-off-by: Aditya Chauhan <aditya.chauhan@intel.com>
---
tests/intel-ci/meson.build | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/intel-ci/meson.build b/tests/intel-ci/meson.build
index 3c7fa28b7..2b3266bbd 100644
--- a/tests/intel-ci/meson.build
+++ b/tests/intel-ci/meson.build
@@ -24,6 +24,7 @@ intelci_files = [
'xe.lnl.eudebug.blocklist.txt',
'xe.multigpu.blocklist.txt',
'xe.nvl.core.blocklist.txt',
+ 'xe.nvl.display.blocklist.txt',
'xe.ptl.core.blocklist.txt',
'xe.ptl.display.blocklist.txt',
'xe.sriov-vf.blocklist.txt',
--
2.34.1
next prev parent reply other threads:[~2026-03-12 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 10:21 [PATCH v3 i-g-t 0/2] intel-ci: Add NVL display and core blocklists Aditya Chauhan
2026-03-12 10:22 ` [PATCH v3 i-g-t 1/2] intel-ci: Add NVL core blocklist Aditya Chauhan
2026-03-12 10:22 ` Aditya Chauhan [this message]
2026-03-12 12:58 ` [PATCH v3 i-g-t 2/2] intel-ci: Add NVL Display blocklist to meson.build Kamil Konieczny
2026-03-12 17:29 ` ✓ Xe.CI.BAT: success for intel-ci: Add NVL display and core blocklists Patchwork
2026-03-12 17:35 ` ✓ i915.CI.BAT: " Patchwork
2026-03-13 17:40 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-13 18:21 ` ✗ Xe.CI.FULL: " 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=20260312102201.53909-3-aditya.chauhan@intel.com \
--to=aditya.chauhan@intel.com \
--cc=himanshu.girotra@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=ramadevi.gandi@intel.com \
--cc=swati2.sharma@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