All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ch, Sai Gowtham" <sai.gowtham.ch@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t] tests/i915/gem_sync.c :Added __for_each_physical_engine to utilize all available engines.
Date: Mon, 6 Apr 2020 09:57:41 +0000	[thread overview]
Message-ID: <5734061626B4B34D8BE569E3846B57A2C26183@BGSMSX107.gar.corp.intel.com> (raw)
In-Reply-To: <158272279684.2462.11970247480138062303@skylake-alporthouse-com>

Patch has been sent  https://patchwork.freedesktop.org/patch/360240/

Thanks,
Gowtham

-----Original Message-----
From: Chris Wilson <chris@chris-wilson.co.uk> 
Sent: Wednesday, February 26, 2020 6:43 PM
To: igt-dev@lists.freedesktop.org; Ch, Sai Gowtham <sai.gowtham.ch@intel.com>
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t] tests/i915/gem_sync.c :Added __for_each_physical_engine to utilize all available engines.

Quoting sai gowtham (2020-02-26 13:02:41)
> @@ -1221,56 +1252,113 @@ igt_main
>  
>                 igt_fork_hang_detector(fd);
>         }

To be safe, I need one to cover the legacy API. To check the bare essential that we can wait on a newly submitted request. A sync_ring, and a sync_all.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-04-06  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 13:02 [igt-dev] [PATCH] [PATCH i-g-t] tests/i915/gem_sync.c :Added __for_each_physical_engine to utilize all available engines sai gowtham
2020-02-26 13:13 ` Chris Wilson
2020-04-06  9:57   ` Ch, Sai Gowtham [this message]
2020-02-26 14:52 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-02-26 16:13 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-27  3:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=5734061626B4B34D8BE569E3846B57A2C26183@BGSMSX107.gar.corp.intel.com \
    --to=sai.gowtham.ch@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.