From: tim.gore@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: thomas.wood@intel.com
Subject: [PATCH i-g-t] tests/gem_exec_params: change flags used in invalid-flags test
Date: Mon, 12 Jan 2015 14:09:49 +0000 [thread overview]
Message-ID: <1421071789-10391-1-git-send-email-tim.gore@intel.com> (raw)
From: Tim Gore <tim.gore@intel.com>
The invalid-flags test in gem_exec_params uses
(I915_EXEC_HANDLE_LUT << 1) as an invalid flag, but this
is no longer invalid for recent android versions, and may
not be invalid in Linux in the future. So I have changed
this test to use (__I915_EXEC_UNKNOWN_FLAGS) instead.
__I915_EXEC_UNKNOWN_FLAGS is defined in i915_drm.h as a
mask of all the undefined flags.
Signed-off-by: Tim Gore <tim.gore@intel.com>
---
tests/gem_exec_params.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/gem_exec_params.c b/tests/gem_exec_params.c
index f63eda9..2a1c544 100644
--- a/tests/gem_exec_params.c
+++ b/tests/gem_exec_params.c
@@ -179,7 +179,7 @@ igt_main
/* HANDLE_LUT and NO_RELOC are already exercised by gem_exec_lut_handle */
igt_subtest("invalid-flag") {
- execbuf.flags = I915_EXEC_RENDER | (I915_EXEC_HANDLE_LUT << 1);
+ execbuf.flags = I915_EXEC_RENDER | (__I915_EXEC_UNKNOWN_FLAGS);
RUN_FAIL(EINVAL);
}
--
2.2.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-01-12 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 14:09 tim.gore [this message]
2015-01-12 16:04 ` [PATCH i-g-t] tests/gem_exec_params: change flags used in invalid-flags test Dave Gordon
2015-01-12 16:14 ` Gore, Tim
2015-01-12 23:26 ` Daniel Vetter
2015-01-13 9:48 ` Gore, Tim
2015-01-13 22:20 ` Daniel Vetter
2015-01-15 13:50 ` Gore, Tim
2015-01-15 17:42 ` Dave Gordon
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=1421071789-10391-1-git-send-email-tim.gore@intel.com \
--to=tim.gore@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@intel.com \
/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