From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [i-g-t V7 0/4] tests/intel/pm: Separate display specific tests from i915_pm_rpm
Date: Wed, 11 Oct 2023 15:47:18 +0530 [thread overview]
Message-ID: <20231011101722.3188258-1-bhanuprakash.modem@intel.com> (raw)
Separate display specific tests from i915_pm_rpm and maintain
in kms_pm_rpm.
Bhanuprakash Modem (4):
tests/intel/pm: Separate display specific tests from i915_pm_rpm
tests/intel/pm_rpm: Split module-reload test
tests/intel/pm_rpm: Fix CI with renamed tests
tests/intel-ci: Add module-reload test to CI
tests/intel-ci/blacklist-pre-merge.txt | 8 +-
tests/intel-ci/blacklist.txt | 1 +
tests/intel-ci/fast-feedback.testlist | 5 +-
tests/intel/i915_pm_rpm.c | 1136 ----------------
tests/intel/kms_pm_rpm.c | 1722 ++++++++++++++++++++++++
tests/meson.build | 1 +
6 files changed, 1731 insertions(+), 1142 deletions(-)
create mode 100644 tests/intel/kms_pm_rpm.c
--
2.40.0
next reply other threads:[~2023-10-11 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 10:17 Bhanuprakash Modem [this message]
2023-10-11 10:17 ` [igt-dev] [i-g-t V7 1/4] tests/intel/pm: Separate display specific tests from i915_pm_rpm Bhanuprakash Modem
2023-10-11 10:17 ` [igt-dev] [i-g-t V7 2/4] tests/intel/pm_rpm: Split module-reload test Bhanuprakash Modem
2023-10-11 10:17 ` [igt-dev] [i-g-t V7 3/4] tests/intel/pm_rpm: Fix CI with renamed tests Bhanuprakash Modem
2023-10-11 14:55 ` Kamil Konieczny
2023-10-11 10:17 ` [igt-dev] [i-g-t V7 4/4] tests/intel-ci: Add module-reload test to CI Bhanuprakash Modem
2023-10-11 14:13 ` Sharma, Swati2
2023-10-11 20:16 ` [igt-dev] ✓ CI.xeBAT: success for tests/intel/pm: Separate display specific tests from i915_pm_rpm (rev4) Patchwork
2023-10-11 20:16 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-10-12 12:04 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20231011101722.3188258-1-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@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