All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: Jeevan B <jeevan.b@intel.com>, igt-dev@lists.freedesktop.org
Cc: animesh.manna@intel.com
Subject: Re: [i-g-t,2/2] RFC: tests/kms_vrr: Add new test to validate LOBF
Date: Wed, 3 Jul 2024 15:46:01 +0530	[thread overview]
Message-ID: <c7df35c7-d641-414d-b032-2cd3d8a47401@intel.com> (raw)
In-Reply-To: <20240626191537.1507452-3-jeevan.b@intel.com>


On 6/27/2024 12:45 AM, Jeevan B wrote:
> Validate pseudo static refresh rate changes in the VRR with
> fixed refresh rate framework.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
Hello Jeevan,

Can you add a HAX patch including this test in fast-feedback for both xe 
and i915,
So we can get results from CI.


Thanks and Regards
Kunal Joshi

  reply	other threads:[~2024-07-03 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 19:15 [PATCH i-g-t 0/2] New test to validate link-off between active regions (LOBF) Jeevan B
2024-06-26 19:15 ` [PATCH i-g-t 1/2] lib/igt_kms: Added library functions for LOBF status Jeevan B
2024-07-17  4:45   ` [i-g-t,1/2] " Joshi, Kunal1
2024-07-17  8:51     ` Manna, Animesh
2024-06-26 19:15 ` [PATCH i-g-t 2/2] RFC: tests/kms_vrr: Add new test to validate LOBF Jeevan B
2024-07-03 10:16   ` Joshi, Kunal1 [this message]
2024-07-03 10:19     ` [i-g-t,2/2] " B, Jeevan
2024-07-03 11:55       ` Manna, Animesh
2024-06-26 21:39 ` ✓ Fi.CI.BAT: success for New test to validate link-off between active regions (LOBF) Patchwork
2024-06-26 21:51 ` ✓ CI.xeBAT: " Patchwork
2024-06-27  7:41 ` ✗ CI.xeFULL: failure " Patchwork
2024-06-28  2:32 ` ✗ Fi.CI.IGT: " 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=c7df35c7-d641-414d-b032-2cd3d8a47401@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=animesh.manna@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.