From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [i-g-t V4 2/7] testplan/kms: Move kms testplan to intel dir
Date: Thu, 3 Aug 2023 01:03:25 +0530 [thread overview]
Message-ID: <20230802193330.3843896-3-bhanuprakash.modem@intel.com> (raw)
In-Reply-To: <20230802193330.3843896-1-bhanuprakash.modem@intel.com>
As this testplan is specific to the Intel hardware, the correct
place for it is inside the tests/i915/.
V2: - Fix the included files path
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
docs/testplan/meson.build | 2 +-
tests/{ => i915}/kms_test_config.json | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename tests/{ => i915}/kms_test_config.json (94%)
diff --git a/docs/testplan/meson.build b/docs/testplan/meson.build
index e838f2eb1..8d3ad952d 100644
--- a/docs/testplan/meson.build
+++ b/docs/testplan/meson.build
@@ -7,7 +7,7 @@ rst2pdf = find_program('rst2pdf', required: false)
stylesheet = join_paths(meson.current_source_dir(), 'testplan.css')
xe_test_config = join_paths(source_root, 'tests', 'xe', 'xe_test_config.json')
-kms_test_config = join_paths(source_root, 'tests', 'kms_test_config.json')
+kms_test_config = join_paths(source_root, 'tests', 'i915', 'kms_test_config.json')
i915_test_config = join_paths(source_root, 'tests', 'i915', 'i915_test_config.json')
check_testlist = []
diff --git a/tests/kms_test_config.json b/tests/i915/kms_test_config.json
similarity index 94%
rename from tests/kms_test_config.json
rename to tests/i915/kms_test_config.json
index 5fbe40bdc..d781822e9 100644
--- a/tests/kms_test_config.json
+++ b/tests/i915/kms_test_config.json
@@ -1,7 +1,7 @@
{
"description": "JSON file to be used to parse KMS documentation",
"name": "Display and KMS Tests for Intel i915 and Xe Drivers",
- "files": [ "chamelium/kms_*.c", "i915/kms_*.c", "kms_*.c" ],
+ "files": [ "../chamelium/kms_*.c", "../kms_*.c", "kms_*.c" ],
"fields": {
"Category": {
"_properties_": {
--
2.40.0
next prev parent reply other threads:[~2023-08-02 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 19:33 [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 1/7] testplan/i915: Exclude non-i915 tests from i915 testplan Bhanuprakash Modem
2023-08-02 19:33 ` Bhanuprakash Modem [this message]
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 3/7] tests/i915/prime_mmap_kms: Add missing documentation Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 4/7] tests/meson.build: Simplify builds for Chamelium targets Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 5/7] tests: Move intel specific tests to new directory Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 6/7] tests/meson.build: Split intel targets based on their nature Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 7/7] tests: Rename all intel specific tests Bhanuprakash Modem
2023-08-02 20:31 ` [igt-dev] ○ CI.xeBAT: info for New dir structure for intel specific tests (rev7) Patchwork
2023-08-02 20:40 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-30 14:44 ` [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Mauro Carvalho Chehab
2023-08-31 15:33 ` Modem, Bhanuprakash
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=20230802193330.3843896-3-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