Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: janga.rahul.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com,
	janga.rahul.kumar@intel.com
Subject: [igt-dev] [PATCH i-g-t 0/3] Add wait fence Negative tests
Date: Wed,  8 Nov 2023 16:52:48 +0530	[thread overview]
Message-ID: <20231108112251.819141-1-janga.rahul.kumar@intel.com> (raw)

From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>

Negative tests to check XE_WAIT_USER_FENCE ioctl.

Janga Rahul Kumar (3):
  tests/intel/xe_waitfence: Add invalid-flag subtest
  tests/intel/xe_waitfence: Add invalid-ops subtest
  tests/intel/xe_waitfence: Add invalid-engine subtest

 tests/intel/xe_waitfence.c | 103 +++++++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)

-- 
2.25.1

             reply	other threads:[~2023-11-08 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 11:22 janga.rahul.kumar [this message]
2023-11-08 11:22 ` [igt-dev] [PATCH i-g-t 1/3] tests/intel/xe_waitfence: Add invalid-flag subtest janga.rahul.kumar
2023-11-09 11:08   ` Dandamudi, Priyanka
2023-11-08 11:22 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel/xe_waitfence: Add invalid-ops subtest janga.rahul.kumar
2023-11-09 11:10   ` Dandamudi, Priyanka
2023-11-08 11:22 ` [igt-dev] [PATCH i-g-t 3/3] tests/intel/xe_waitfence: Add invalid-engine subtest janga.rahul.kumar
2023-11-09 11:12   ` Dandamudi, Priyanka
2023-11-08 12:05 ` [igt-dev] ✓ CI.xeBAT: success for Add wait fence Negative tests (rev2) Patchwork
2023-11-08 12:07 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-08 18:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  9:16 [igt-dev] [PATCH i-g-t 0/3] Add wait fence Negative tests janga.rahul.kumar

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=20231108112251.819141-1-janga.rahul.kumar@intel.com \
    --to=janga.rahul.kumar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ramadevi.gandi@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