From: tim.gore@intel.com
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH] intel-gpu-tools: move kms_fence_pin_leak to single test list
Date: Wed, 4 Jun 2014 09:32:54 +0100 [thread overview]
Message-ID: <1401870774-8649-1-git-send-email-tim.gore@intel.com> (raw)
From: Tim Gore <tim.gore@intel.com>
In Makefile.sources, kms_fence_pin_leak was in the "Multi" test list,
ie tests with subtests, whereas it is actually simple/single test.
This was confusing the Android script for enumerating tests.
Signed-off-by: Tim Gore <tim.gore@intel.com>
---
tests/Makefile.sources | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/Makefile.sources b/tests/Makefile.sources
index eca4af9..e4c23b3 100644
--- a/tests/Makefile.sources
+++ b/tests/Makefile.sources
@@ -62,7 +62,6 @@ TESTS_progs_M = \
kms_addfb \
kms_cursor_crc \
kms_fbc_crc \
- kms_fence_pin_leak \
kms_flip \
kms_flip_tiling \
kms_mmio_vs_cs_flip \
@@ -137,6 +136,7 @@ TESTS_progs = \
gen3_render_tiledy_blits \
gen7_forcewake_mt \
kms_sink_crc_basic \
+ kms_fence_pin_leak \
pm_psr \
pm_rc6_residency \
prime_udl \
--
1.9.2
next reply other threads:[~2014-06-04 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 8:32 tim.gore [this message]
2014-06-04 16:15 ` [PATCH] intel-gpu-tools: move kms_fence_pin_leak to single test list Daniel Vetter
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=1401870774-8649-1-git-send-email-tim.gore@intel.com \
--to=tim.gore@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