public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
* [PATCH i-g-t v1] tests/kms_explicit_fence: Separate feature tag block from test description
@ 2026-03-25  8:39 Sowmiya S
  2026-03-25 10:31 ` ✓ Xe.CI.BAT: success for " Patchwork
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: Sowmiya S @ 2026-03-25  8:39 UTC (permalink / raw)
  To: igt-dev; +Cc: swati2.sharma, Sowmiya S

Split the comment into two blocks: one for the
feature tags and one for the long-form explanation
of the test. This improves readability and ensures
documentation generators treat the sections separately.

Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
---
 tests/kms_explicit_fence.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/kms_explicit_fence.c b/tests/kms_explicit_fence.c
index a7d127c93..400fef939 100644
--- a/tests/kms_explicit_fence.c
+++ b/tests/kms_explicit_fence.c
@@ -9,7 +9,9 @@
  * Description: Test explicit fencing with multiple planes and mixed fence states
  * Driver requirement: i915, xe
  * Mega feature: General Display Features
- *
+ */
+
+/**
  * This test validates correct handling of explicit fences when multiple planes
  * are updated in a single atomic commit with different fence states. This is
  * critical for catching fence synchronization bugs where the driver might:
-- 
2.43.0


^ permalink raw reply related	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2026-03-25 17:20 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-25  8:39 [PATCH i-g-t v1] tests/kms_explicit_fence: Separate feature tag block from test description Sowmiya S
2026-03-25 10:31 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-25 10:36 ` [PATCH i-g-t v1] " Sharma, Swati2
2026-03-25 11:07 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-25 16:50 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-25 17:19 ` ✗ i915.CI.Full: failure " Patchwork

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox