From: himanshu.girotra@intel.com
To: ramadevi.gandi@intel.com, igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t] tests/intel: Adjust test documentation
Date: Mon, 6 Apr 2026 17:40:18 +0530 [thread overview]
Message-ID: <20260406121018.19963-1-himanshu.girotra@intel.com> (raw)
From: Himanshu Girotra <himanshu.girotra@intel.com>
Fix multiple-parent warnings in test list generation by correcting
Category and Mega feature metadata fields across test files
Signed-off-by: Himanshu Girotra <himanshu.girotra@intel.com>
---
tests/intel/xe_multigpu_svm.c | 2 +-
tests/intel/xe_sysfs_preempt_timeout.c | 2 +-
tests/intel/xe_sysfs_timeslice_duration.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/intel/xe_multigpu_svm.c b/tests/intel/xe_multigpu_svm.c
index 2ae0b950f..e04e9692e 100644
--- a/tests/intel/xe_multigpu_svm.c
+++ b/tests/intel/xe_multigpu_svm.c
@@ -27,7 +27,7 @@
* Description: Validate multi-GPU Shared Virtual Memory (SVM) features,
* including cross-GPU access, atomic operations, coherency
*
- * Category: Multi-GPU
+ * Category: Core
* Mega feature: MultiGPU
* Sub-category: SVM, memory management, performance
* Functionality: Multi-GPU SVM, migration, coherency, atomic ops
diff --git a/tests/intel/xe_sysfs_preempt_timeout.c b/tests/intel/xe_sysfs_preempt_timeout.c
index 725707bf6..9ddedf98f 100644
--- a/tests/intel/xe_sysfs_preempt_timeout.c
+++ b/tests/intel/xe_sysfs_preempt_timeout.c
@@ -6,7 +6,7 @@
/**
* TEST: sysfs preempt timeout
* Category: Core
- * Mega feature: SysMan
+ * Mega feature: General Core features
* Sub-category: SysMan tests
* Functionality: sysfs preempt timeout
* Feature: SMI, context
diff --git a/tests/intel/xe_sysfs_timeslice_duration.c b/tests/intel/xe_sysfs_timeslice_duration.c
index 93b97f805..6aad2902b 100644
--- a/tests/intel/xe_sysfs_timeslice_duration.c
+++ b/tests/intel/xe_sysfs_timeslice_duration.c
@@ -9,7 +9,7 @@
/**
* TEST: sysfs timeslice duration
* Category: Core
- * Mega feature: SysMan
+ * Mega feature: General Core features
* Sub-category: SysMan tests
* Functionality: sysfs timslice duration
* Feature: SMI, context
--
2.50.1
next reply other threads:[~2026-04-06 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 12:10 himanshu.girotra [this message]
2026-04-06 12:15 ` [PATCH i-g-t] tests/intel: Adjust test documentation Girotra, Himanshu
2026-04-06 13:37 ` ✓ Xe.CI.BAT: success for tests/intel: Adjust test documentation (rev3) Patchwork
2026-04-06 13:42 ` ✓ i915.CI.BAT: " Patchwork
2026-04-06 15:39 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-06 15:57 ` ✓ Xe.CI.FULL: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-11-04 17:58 [PATCH i-g-t] tests/intel: Adjust test documentation himanshu.girotra
2025-11-05 2:05 ` Dandamudi, Priyanka
2025-11-10 5:55 ` Girotra, Himanshu
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=20260406121018.19963-1-himanshu.girotra@intel.com \
--to=himanshu.girotra@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramadevi.gandi@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