Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
Subject: Re: [i-g-t,1/2] tests/kms_bw: add subtest for only connected outputs
Date: Wed, 26 Jun 2024 10:31:37 +0530	[thread overview]
Message-ID: <aabb925a-b578-407b-bbdd-05d6c019b539@intel.com> (raw)
In-Reply-To: <20240619080408.1161329-2-kunal1.joshi@intel.com>

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]


On 6/19/2024 1:34 PM, Kunal Joshi wrote:
> forcing DP connector doesn't work well and tests are skipping
> with unsupported mode, add new test which runs test on connected
> outputs only.
>
> v2: added debug print for better clarity of skips on unsupported mode
>
> v3: added new line in info
>      moved skip after test_init
>      updated test_init logic based on physical flag
>
> Cc: Aurabindo Pillai<aurabindo.pillai@amd.com>
> Signed-off-by: Kunal Joshi<kunal1.joshi@intel.com>
> Reviewed-by: Aurabindo Pillai<aurabindo.pillai@amd.com>

Hello Aurabindo,

Since the changes are minor i am keeping your rb, planning to merge this 
by EOD.
Please let me know if you see any concerns.


Thanks and Regards
Kunal Joshi

[-- Attachment #2: Type: text/html, Size: 1381 bytes --]

  parent reply	other threads:[~2024-06-26  5:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  8:04 [PATCH i-g-t 0/2] add subtest in kms_bw for connected outputs only Kunal Joshi
2024-06-19  8:04 ` [PATCH i-g-t 1/2] tests/kms_bw: add subtest for only connected outputs Kunal Joshi
2024-06-23 16:26   ` [i-g-t,1/2] " Joshi, Kunal1
2024-06-26  5:01   ` Joshi, Kunal1 [this message]
2024-06-26 13:21     ` Pillai, Aurabindo
2024-06-19  8:04 ` [PATCH i-g-t 2/2] HAX patch do not merge Kunal Joshi
2024-06-19 19:30 ` ✓ CI.xeBAT: success for add subtest in kms_bw for connected outputs only Patchwork
2024-06-19 19:30 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-06-20  2:51 ` ✓ CI.xeFULL: success " 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=aabb925a-b578-407b-bbdd-05d6c019b539@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=aurabindo.pillai@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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