From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Sowmiya S <sowmiya.s@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v1] tests/kms_explicit_fence: Separate feature tag block from test description
Date: Wed, 25 Mar 2026 16:06:07 +0530 [thread overview]
Message-ID: <b6ae2e35-b7c9-47f8-a105-c728ca6e7f55@intel.com> (raw)
In-Reply-To: <20260325083947.765016-1-sowmiya.s@intel.com>
Hi Sowmiya,
On 25-03-2026 02:09 pm, Sowmiya S wrote:
> 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.
Patch LGTM
Reviewed-by: Swati Sharma <swati2.sharma@intel.com>
>
> 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:
next prev parent reply other threads:[~2026-03-25 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Sharma, Swati2 [this message]
2026-03-25 11:07 ` ✓ i915.CI.BAT: " 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=b6ae2e35-b7c9-47f8-a105-c728ca6e7f55@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=sowmiya.s@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