Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 2/4] tests: Move gem_bad_address to hw-tests
Date: Wed, 13 Dec 2017 14:58:14 +0200	[thread overview]
Message-ID: <20171213125816.18371-3-petri.latvala@intel.com> (raw)
In-Reply-To: <20171213125816.18371-1-petri.latvala@intel.com>

Since the test is considered to be HW focused, meaning that it doesn't
really exercise the driver but rather an HW feature, it is placed in
tests/hw-tests.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Antonio Argenziano <antonio.argenziano@intel.com>
---
 tests/Makefile.sources                 | 1 -
 tests/hw-tests/Makefile.sources        | 1 +
 tests/{ => hw-tests}/gem_bad_address.c | 0
 tests/hw-tests/meson.build             | 1 +
 tests/meson.build                      | 1 -
 5 files changed, 2 insertions(+), 2 deletions(-)
 rename tests/{ => hw-tests}/gem_bad_address.c (100%)

diff --git a/tests/Makefile.sources b/tests/Makefile.sources
index e4e06d01..29dfd9cd 100644
--- a/tests/Makefile.sources
+++ b/tests/Makefile.sources
@@ -264,7 +264,6 @@ HANG = \
 	gem_bad_batch \
 	gem_hang \
 	gem_bad_blit \
-	gem_bad_address \
 	gem_non_secure_batch \
 	$(NULL)
 
diff --git a/tests/hw-tests/Makefile.sources b/tests/hw-tests/Makefile.sources
index a224da7c..1fb3ed9e 100644
--- a/tests/hw-tests/Makefile.sources
+++ b/tests/hw-tests/Makefile.sources
@@ -1,2 +1,3 @@
 hw_tests = \
+	 gem_bad_address \
 	 $(NULL)
diff --git a/tests/gem_bad_address.c b/tests/hw-tests/gem_bad_address.c
similarity index 100%
rename from tests/gem_bad_address.c
rename to tests/hw-tests/gem_bad_address.c
diff --git a/tests/hw-tests/meson.build b/tests/hw-tests/meson.build
index 32bb637d..848d113e 100644
--- a/tests/hw-tests/meson.build
+++ b/tests/hw-tests/meson.build
@@ -1,4 +1,5 @@
 hw_test_progs = [
+	'gem_bad_address',
 ]
 
 hw_test_deps = [ igt_deps ]
diff --git a/tests/meson.build b/tests/meson.build
index 8ab16a70..5eef1bd6 100644
--- a/tests/meson.build
+++ b/tests/meson.build
@@ -301,7 +301,6 @@ hang_progs = [
 	'gem_bad_batch',
 	'gem_hang',
 	'gem_bad_blit',
-	'gem_bad_address',
 	'gem_non_secure_batch',
 ]
 foreach prog : hang_progs
-- 
2.14.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-12-13 12:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 12:58 [PATCH i-g-t 0/4] Create a new directory for hardware-targeting tests Petri Latvala
2017-12-13 12:58 ` [PATCH i-g-t 1/4] tests: Add a hw-tests subdirectory Petri Latvala
2017-12-13 12:58 ` Petri Latvala [this message]
2017-12-13 13:26   ` [PATCH i-g-t 2/4] tests: Move gem_bad_address to hw-tests Chris Wilson
2017-12-15 19:43     ` Antonio Argenziano
2017-12-13 12:58 ` [PATCH i-g-t 3/4] hw-tests: Fix and update gem_bad_address Petri Latvala
2017-12-15 20:46   ` Chris Wilson
2017-12-13 12:58 ` [PATCH i-g-t 4/4] run-tests.sh: Allow users to override IGT_TEST_ROOT Petri Latvala
2017-12-13 16:04   ` Arkadiusz Hiler
2017-12-13 16:41 ` ✓ Fi.CI.BAT: success for Create a new directory for hardware-targeting tests Patchwork
2017-12-13 18:31 ` ✓ 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=20171213125816.18371-3-petri.latvala@intel.com \
    --to=petri.latvala@intel.com \
    --cc=intel-gfx@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