From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v5 0/3] Fix kms_psr2_sf test and add new test for FB_DAMAGE_CLIPS plane property
Date: Fri, 3 Dec 2021 21:58:50 +0530 [thread overview]
Message-ID: <20211203162853.14262-1-jeevan.b@intel.com> (raw)
Change kms_psr2_sf test design, rename igt_debug_manual_check, patch the igt
functions igt_debug_wait_for_keypress() to assert if "all" is supplied and
change testcase design and add simple test cases to use FB_DAMAGE_CLIPS plane property.
Deepak Rawat (1):
tests/kms_atomic: Add a new test case for FB_DAMAGE_CLIPS plane
property
Jeevan B (2):
lib/igt_aux: Rename igt_debug_manual_check and assert check if all is
supplied
tests/kms_psr2_sf: Change testcase design
lib/igt_aux.c | 9 +-
lib/igt_aux.h | 2 +-
tests/i915/kms_dsc.c | 2 +-
tests/i915/kms_psr.c | 2 +-
tests/i915/kms_psr2_sf.c | 28 ++---
tests/kms_atomic.c | 219 +++++++++++++++++++++++++++++++++++++++
6 files changed, 242 insertions(+), 20 deletions(-)
--
2.19.1
next reply other threads:[~2021-12-03 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:28 Jeevan B [this message]
2021-12-03 16:28 ` [igt-dev] [PATCH i-g-t v5 1/3] lib/igt_aux: Rename igt_debug_manual_check and assert check if all is supplied Jeevan B
2021-12-03 16:28 ` [igt-dev] [PATCH i-g-t v5 2/3] tests/kms_psr2_sf: Change testcase design Jeevan B
2021-12-03 16:28 ` [igt-dev] [PATCH i-g-t v5 3/3] tests/kms_atomic: Add a new test case for FB_DAMAGE_CLIPS plane property Jeevan B
2021-12-03 16:52 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix kms_psr2_sf test and add new test for FB_DAMAGE_CLIPS plane property (rev5) Patchwork
2021-12-04 0:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-12-08 12:28 ` B, Jeevan
2021-12-08 16:03 ` Vudum, Lakshminarayana
2021-12-08 16:21 ` B, Jeevan
2021-12-08 17:54 ` Vudum, Lakshminarayana
2021-12-08 18:08 ` B, Jeevan
2021-12-08 18:09 ` Vudum, Lakshminarayana
2021-12-08 17:00 ` [igt-dev] ✓ Fi.CI.IGT: 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=20211203162853.14262-1-jeevan.b@intel.com \
--to=jeevan.b@intel.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