From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Petri Latvala <petri.latvala@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915: Fix is_physical_engine advancement
Date: Wed, 29 Jan 2020 14:35:38 +0200 [thread overview]
Message-ID: <20200129123538.GA6475@intel.intel> (raw)
In-Reply-To: <20200129121602.1106978-1-chris@chris-wilson.co.uk>
Hi Chris,
On Wed, Jan 29, 2020 at 12:16:02PM +0000, Chris Wilson wrote:
> Update the local var e after iterating to the next engine when searching
> for the next non-virtual engine. Otherwise, it is prone to loop forever.
Do I remember correctly that you sent this once already?
In any case,
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Thanks,
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] lib/i915: Fix is_physical_engine advancement
Date: Wed, 29 Jan 2020 14:35:38 +0200 [thread overview]
Message-ID: <20200129123538.GA6475@intel.intel> (raw)
In-Reply-To: <20200129121602.1106978-1-chris@chris-wilson.co.uk>
Hi Chris,
On Wed, Jan 29, 2020 at 12:16:02PM +0000, Chris Wilson wrote:
> Update the local var e after iterating to the next engine when searching
> for the next non-virtual engine. Otherwise, it is prone to loop forever.
Do I remember correctly that you sent this once already?
In any case,
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-29 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 12:16 [igt-dev] [PATCH i-g-t] lib/i915: Fix is_physical_engine advancement Chris Wilson
2020-01-29 12:16 ` [Intel-gfx] " Chris Wilson
2020-01-29 12:35 ` Andi Shyti [this message]
2020-01-29 12:35 ` Andi Shyti
2020-01-29 12:37 ` [igt-dev] " Chris Wilson
2020-01-29 12:37 ` [Intel-gfx] " Chris Wilson
2020-01-29 13:42 ` [igt-dev] ✗ Fi.CI.BAT: failure for " 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=20200129123538.GA6475@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=tvrtko.ursulin@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 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.