From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t 0/3] tests/intel/kms_joiner: Add a new test to validate non-joiner mode
Date: Tue, 4 Feb 2025 23:57:31 +0530 [thread overview]
Message-ID: <20250204182734.793645-1-jeevan.b@intel.com> (raw)
Added new lib changes to find non_joiner_mode and updated test.
Signed-off-by: Jeevan B <jeevan.b@intel.com>
Jeevan B (3):
lib/igt_kms: Add lib changes to check joiner is enabled
lib/igt_kms: Add support to check joiner mode limit
tests/intel/kms_joiner: Add a new test to validate non-joiner mode
lib/igt_kms.c | 66 ++++++++++++++++++++++++++++++++++++++++
lib/igt_kms.h | 3 ++
tests/intel/kms_joiner.c | 54 ++++++++++++++++++++++++++++++++
3 files changed, 123 insertions(+)
--
2.25.1
next reply other threads:[~2025-02-04 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 18:27 Jeevan B [this message]
2025-02-04 18:27 ` [PATCH i-g-t 1/3] lib/igt_kms: Add lib changes to check joiner is enabled Jeevan B
2025-02-07 5:51 ` Karthik B S
2025-02-04 18:27 ` [PATCH i-g-t 2/3] lib/igt_kms: Add support to check joiner mode limit Jeevan B
2025-02-07 8:22 ` Karthik B S
2025-02-04 18:27 ` [PATCH i-g-t 3/3] tests/intel/kms_joiner: Add a new test to validate non-joiner mode Jeevan B
2025-02-07 8:25 ` Karthik B S
2025-02-05 1:48 ` ✗ GitLab.Pipeline: warning for tests/intel/kms_joiner: Add a new test to validate non-joiner mode (rev5) Patchwork
2025-02-05 2:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-05 2:21 ` ✓ i915.CI.BAT: " Patchwork
2025-02-05 9:08 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-05 10:14 ` ✗ i915.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 18:36 [PATCH i-g-t 0/3] tests/intel/kms_joiner: Add a new test to validate non-joiner mode Jeevan B
2025-02-12 7:36 Jeevan B
2025-02-12 7:21 ` B, Jeevan
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=20250204182734.793645-1-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@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