Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <janga.rahul.kumar@intel.com>
Cc: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] Add VM error capture tests
Date: Thu, 8 Jun 2023 14:11:09 +0000	[thread overview]
Message-ID: <ZIHhfQZsk8P2pCbN@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20230607080352.950226-1-janga.rahul.kumar@intel.com>

On Wed, Jun 07, 2023 at 01:33:50PM +0530, janga.rahul.kumar@intel.com wrote:
> From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
> 
> Add tests to check VM error capture.
> 
> Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
> 

This uAPI is changing soon, please don't more tests for it.

Matt

> Janga Rahul Kumar (2):
>   tests/xe_vm.c: Add VM bind error capture test
>   tests/xe_vm.c: Add Negative test to VM error capture
> 
>  tests/xe/xe_vm.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 81 insertions(+)
> 
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2023-06-08 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  8:03 [igt-dev] [PATCH i-g-t 0/2] Add VM error capture tests janga.rahul.kumar
2023-06-07  8:03 ` [igt-dev] [PATCH i-g-t 1/2] tests/xe_vm.c: Add VM bind error capture test janga.rahul.kumar
2023-06-07  8:03 ` [igt-dev] [PATCH i-g-t 2/2] tests/xe_vm.c: Add Negative test to VM error capture janga.rahul.kumar
2023-06-09  5:44   ` Dandamudi, Priyanka
2023-06-09 12:59     ` Kamil Konieczny
2023-06-07  8:26 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add VM error capture tests Patchwork
2023-06-07  8:40 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 19:58 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-08 14:11 ` Matthew Brost [this message]

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=ZIHhfQZsk8P2pCbN@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janga.rahul.kumar@intel.com \
    --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