Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nakshtra.goyal@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com
Cc: janga.rahul.kumar@intel.com, sai.gowtham.ch@intel.com,
	kamil.konieczny@linux.intel.com
Subject: [PATCH i-g-t, v5 0/2] tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe
Date: Thu,  1 Aug 2024 20:37:35 +0530	[thread overview]
Message-ID: <20240801150737.3700254-1-nakshtra.goyal@intel.com> (raw)

From: Nakshtra Goyal <nakshtra.goyal@intel.com>

Changing variable initialisation type, sorting igt headers,adding spaces
according to comments in v3

Adding test in fast_feedback to check it xe BAT in CI

Nakshtra Goyal (2):
  tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe
  HAX/DO_NOT_MERGE: xe-fast-feedback: test  xe_sysfs_preempt_timeout

 tests/intel-ci/xe-fast-feedback.testlist |   2 +
 tests/intel/xe_sysfs_preempt_timeout.c   | 218 +++++++++++++++++++++++
 tests/meson.build                        |   1 +
 3 files changed, 221 insertions(+)
 create mode 100644 tests/intel/xe_sysfs_preempt_timeout.c

-- 
2.34.1


             reply	other threads:[~2024-08-01 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 15:07 nakshtra.goyal [this message]
2024-08-01 15:07 ` [PATCH i-g-t, v5 1/2] tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe nakshtra.goyal
2024-08-01 19:04   ` [PATCH i-g-t,v5 " Kamil Konieczny
2024-08-01 15:07 ` [PATCH i-g-t, v5 2/2] HAX/DO_NOT_MERGE: xe-fast-feedback: test xe_sysfs_preempt_timeout nakshtra.goyal
2024-08-01 17:07 ` ✗ GitLab.Pipeline: warning for tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe (rev5) Patchwork
2024-08-01 17:28 ` ✓ CI.xeBAT: success " Patchwork
2024-08-01 17:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-01 21:05 ` ✗ CI.xeFULL: " 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=20240801150737.3700254-1-nakshtra.goyal@intel.com \
    --to=nakshtra.goyal@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janga.rahul.kumar@intel.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=ramadevi.gandi@intel.com \
    --cc=sai.gowtham.ch@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