Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Swati Sharma <swati2.sharma@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [v4 0/4] enable feature-discovery tests
Date: Tue, 12 Sep 2023 12:31:45 +0530	[thread overview]
Message-ID: <20230912070149.1305060-1-swati2.sharma@intel.com> (raw)

Enable feature-discovery tests for xe. Add testplan documentation.
Add new dp-mst feature discovery test.

Swati Sharma (4):
  tests: rename feature_discovery to kms_feature_discovery
  tests/kms_feature_discovery: add testplan documentation
  tests/intel-ci: remove feature_discovery from blocklist
  tests/kms_feature_discovery: detect mst configuration

 tests/intel-ci/xe.blocklist.txt               |  1 -
 ...re_discovery.c => kms_feature_discovery.c} | 73 ++++++++++++++++++-
 tests/meson.build                             |  2 +-
 3 files changed, 73 insertions(+), 3 deletions(-)
 rename tests/{feature_discovery.c => kms_feature_discovery.c} (60%)

-- 
2.25.1

             reply	other threads:[~2023-09-12  7:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  7:01 Swati Sharma [this message]
2023-09-12  7:01 ` [igt-dev] [v4 1/4] tests: rename feature_discovery to kms_feature_discovery Swati Sharma
2023-09-12  7:01 ` [igt-dev] [v4 2/4] tests/kms_feature_discovery: add testplan documentation Swati Sharma
2023-09-12 15:37   ` Modem, Bhanuprakash
2023-09-12  7:01 ` [igt-dev] [v4 3/4] tests/intel-ci: remove feature_discovery from blocklist Swati Sharma
2023-09-12  7:01 ` [igt-dev] [v4 4/4] tests/kms_feature_discovery: detect mst configuration Swati Sharma
2023-09-12  7:47 ` [igt-dev] ✓ Fi.CI.BAT: success for enable feature-discovery tests (rev3) Patchwork
2023-09-12  8:07 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-12  8:56 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-13  9:30 ` [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=20230912070149.1305060-1-swati2.sharma@intel.com \
    --to=swati2.sharma@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