From: Mohammed Thasleem <mohammed.thasleem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH v1 0/2] kms lease
Date: Thu, 21 Apr 2022 19:06:36 +0530 [thread overview]
Message-ID: <20220421133638.1492-1-mohammed.thasleem@intel.com> (raw)
kms lease test check
Mohammed Thasleem (2):
tests/kms_lease: Terminate lease fd before subtests execution
HAX: Check kms lease
tests/intel-ci/xe-fast-feedback.testlist | 21 ++
tests/kms_lease.c | 261 +++++++++++------------
2 files changed, 151 insertions(+), 131 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-26 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 13:36 Mohammed Thasleem [this message]
2022-04-21 13:36 ` [igt-dev] [PATCH v1 1/2] tests/kms_lease: Terminate lease fd before subtests execution Mohammed Thasleem
2022-04-21 13:36 ` [igt-dev] [PATCH v1 2/2] HAX: Check kms lease Mohammed Thasleem
2023-08-26 19:34 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-08-26 19:58 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-08-26 20:10 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-26 21:18 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20220421133638.1492-1-mohammed.thasleem@intel.com \
--to=mohammed.thasleem@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