Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, santhosh.reddy.guddati@intel.com,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH i-g-t 0/2] Group all force_hdcp14 tests together
Date: Mon, 11 May 2026 09:11:36 +0530	[thread overview]
Message-ID: <20260511034137.93127-1-suraj.kandpal@intel.com> (raw)

Group all force_hdcp14 tests together. This is to make it easier to
run all force_hdcp14 tests together and also to make the test
suite more organized.
Moreover, MST Dock ends up in a bad state after running the force_hdcp14 tests,
so grouping them together will help in avoiding running other tests after
the force_hdcp14 tests.
Only expeptions are the DPMS and suspend resume tests as they help
get the MST Dock out of the bad state.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Suraj Kandpal (2):
  tests/kms_content_protection: Group all force_hdcp14 tests together
  tests/kms_content_protection: Group all MST force_hdcp14 tests
    together

 tests/kms_content_protection.c | 96 +++++++++++++++++-----------------
 1 file changed, 48 insertions(+), 48 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-05-11  3:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  3:41 Suraj Kandpal [this message]
2026-05-11  3:41 ` [PATCH i-g-t 1/2] tests/kms_content_protection: Group all force_hdcp14 tests together Suraj Kandpal
2026-05-12  4:43   ` Reddy Guddati, Santhosh
2026-05-11  3:41 ` [PATCH i-g-t 2/2] tests/kms_content_protection: Group all MST " Suraj Kandpal
2026-05-12  4:45   ` Reddy Guddati, Santhosh
2026-05-11 21:23 ` ✓ i915.CI.BAT: success for Group all " Patchwork
2026-05-11 21:55 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 23:52 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-12  5:02 ` ✗ i915.CI.Full: " 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=20260511034137.93127-1-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=santhosh.reddy.guddati@intel.com \
    --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