From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v1] tests/kms_explicit_fence: Separate feature tag block from test description
Date: Wed, 25 Mar 2026 14:09:47 +0530 [thread overview]
Message-ID: <20260325083947.765016-1-sowmiya.s@intel.com> (raw)
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
next reply other threads:[~2026-03-25 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 8:39 Sowmiya S [this message]
2026-03-25 10:31 ` ✓ Xe.CI.BAT: success for tests/kms_explicit_fence: Separate feature tag block from test description 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
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=20260325083947.765016-1-sowmiya.s@intel.com \
--to=sowmiya.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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